Print

[kamil445]

Hi,

Since 3-4 days geolocation is wrong for "2001:470:71:447::/64".

3-4 days ago bgp.he.net says geoloc "89-650Czersk / Pomorskie / Poland".
Now is USA and i can't access sites restricted only for Poland IP's

Code: [Select]

contact:Street-Address:760 Mission Ct
contact:City:Fremont
contact:Province:CA
contact:Postal-Code:94539
contact:Country-Code:US
Please, if possible restore previous record.

Thanks!

[jwinius]

My network may have had the same problem for the past few days. Here in the Netherlands, my tunnel suddenly stopped working late Wednesday evening, However, late this afternoon it started again just as mysteriously. I was fairly certain the problem was with HE. Damned irritating!

[tjeske]

Also my prefix that was correctly attributed to Germany (using Berlin tunnel endpoint) is now showing Fremont, CA as location.

[broquea]

Looks like our rwhois wasn't responding correctly. It should be now, so ideally all those 3rd party systems that make up their databases, update.

[kamil445]

Again geolocation is wrong since maybe 6-7 days

[altadenamd]

One of my blocks is missing from rwhois (the other 3 main ones are fine; both /64s are fine)..  The look at this was prompted by ARIN wanting to cancel my HE contact (I assume that this is because the rwhois is considered working...)
The blocks are all properly routed (I'm using the missing one for this message).  As far as geolocation goes, I've had good luck using maxmind's web portal to correct things (the missing block gets assigned to hong kong fairly often for some reason)  Still wish that either (or both) of Verizon and Charter/Spectrum would turn up V6 for customers; both of them have dual-stack core (and Spectrum provides V6 just fine in former RR areas, just not Charter...)  (and VZW LTE is all V6, like TMobile pioneered..  VZ FIOS isn't VZW, though.)

[snarked]

Geolocation databases are THIRD party data.  HE has little control.