bgp.tools being served via 13 authoritative name servers (via 3 different providers + in house NS):

```
$ dig +short ns bgp.tools
ns1.exoscale.ch.
ns-721.awsdns-26.net.
ns-1329.awsdns-38.org.
ns4-35.azure-dns.info.
ns3-35.azure-dns.org.
ns1.exoscale.io.
ns-302.awsdns-37.com.
ns-1799.awsdns-32.co.uk.
ns1.exoscale.net.
ns1-35.azure-dns.com.
ns2-35.azure-dns.net.
ns1.exoscale.com.
backup-ns.bgp.tools.
```

#bgptools #nameservers #dns

For @tschaefer
#Telekom #Roaming in NL with #Odido
Only #DualStack works. #IPv6only is not possible.

#bgptools

On a #FrecciaRossa (must be Italian for f*ing fast train) between Milano and Roma.

Can't help but measure its Internet, one thing I noticed is that COLT (AS8220) providers internet connectivity for onboard free wifi, and on all 3 devices I checked the external IP is the same. So maybe the whole train is on a single IPv4 address at 300km/h?

Kudos #BGPtools for having this on the front page, so it was a breeze to ask my 12yo to check this!

Deleted my last BGP route collector session with bgp.tools, because I wanted to switch it to a different server.
Can't add another one, I now have 0, no more available.

Pity D:

Are there similar services?

#bgp #bgptools

Does anyone know where bgp.tools gets their forward / reverse DNS data from, i.e. which hostnames they forward and which IPs they reverse resolve? And how often is the data updated? Can I as an IP prefix owner trigger the update?

#bgptools #bgp

Awesome to read that a fellow student and friend of mine at the #utwente, the Netherlands was cited by Bellingcat yesterday.

Besides that, they did an interesting introduction on what intelligence #bgptools offers.

Check out the write-up on Bellingcat

#bgp #routing #bellingcat