[tor-relays] bridge in limbo after new ip assigned

[mossy_road_523--- via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>]

I run an obfs4 bridge. The bridge had been up, operational and carrying (light) traffic for almost 60 days when my ISP assigned me a new address. I wasn't able to repair the bridge for 4 or 5 days. When I did get to it, I registered with a DDNS service, and in my torrc I replaced the hard coded IP with the new domain name I registered. After making that change I restarted the bridge. Logs all looked fine, it booted up to 100%, and reported that the IP was externally reachable (Excellent!). It has been running for 5 days now. It frequently reports having 20 or 25 circuits open (mostly hs_vanguards and conflux_linked; occasionally a "General" purpose circuit). Traffic has been extremely sparse.

Even though the bridge seems healthy from my end, I get mixed results from the external checks: 
  * Tor Metrics Relay Search site says the bridge is down, and shows 0 bytes moved and 0 users for the past many days. 
  * bridges.torproject.org/status page always report the bridge as "dysfunctional." 
  * Tor Project Tor Reachability Checker always reports "TCP port is reachable!"

I don't mind the "broken" status pages so much, but the fact the bridge itself reports carrying very little (although non-zero) traffic has me concerned.
Can any one shed any light on what might be happening, what I could try to further debug this, etc.?

Happy to provide snippets of my torrc or any other info that might be helpful.

Bridge id is 744DA6E2E2BCB93999C8B16C1C185BA06DFFA447
Tor Metrics page for the bridge: https://metrics.torproject.org/rs.html#details/744DA6E2E2BCB93999C8B16C1C185BA06DFFA447
bridges-status site: https://bridges.torproject.org/status?id=744DA6E2E2BCB93999C8B16C1C185BA06DFFA447

Thanks much for any help.
_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx