The August 2024 changelog is out! , This month changes include:. * BGP Flapping / Churn detection.* Prefix counts on AS-SET pages.* NAT64 addresses are now automatically translated in the search bar to their IPv4 counterparts

Airtel fixed the bogus announcement at 04:40 UTC today. Looking back at the data, Orange/GTT/NTT/Cogent also accepted the /3 via Sparkle (TI), from Airtel. GTT's acceptance was down to a (now fixed) JunOS config gotcha

This halfed the number of RPKI ROV Validating ASNs according to (via RIPE Atlas) because those networks accepted the /3 and one of the probe IPs is inside 96.0.0.0/3

Looks like AS9498 (Bharti Airtel) typod a /32, /31 or /30. And turned it into a /3 (aka, 12.5% of the IPv4 internet) and other carriers (At least TI & GTT) accepted it!

RT @DougMadory: Partial de-peering between Cogent (AS174) and Tata (AS6453) yesterday, first reported by @bgptools. Here's @kentikinc's vi….

This seems to come off the back of Cogent trying to establish a market in APAC, and the main players in that region not wanting to have their market eaten away by Cogent (To be fair, Cogent is very good at getting prices down, and APAC is still quite expensive per mbps).

Due to this Networks that are single homed behind AS6453 (in APAC) or AS174 will not be able to reach each other. This is similar but more serious to the previous regional NTT-Cogent depeerings (since the NTT ones "just" increased latency by routing via the US instead).

(The previous TATA-Cogent Full depeering post was wrong). It appears that TATA-Cogent have partially depeered in APAC. Cogent can't see APAC (notably India) routes anymore. It seems based on statements Cogent has initiated this depeering (Some EU/US routes seem to still be find)

3. Small fixes/changes. Like every month, there are a number of smaller improvements and fixes that are not blockbuster features, here are this months smaller fixes and changes!. Find the full changelog here: !. 🧵3/3

2. Automatic Hijack Detection List generation. Paying customers who have hijack detection enabled can now have their hijack lists automatically updated by the website itself, so new prefixes don't slip through the cracks!. 🧵2/3

The May 2024 changelog is out!. Major changes include:. 1. Route Servers on propagation graphs, and more. New display options for propagation graphs, including IXP visibility . 🧵1/3

You can now change display options for the propagation graphs!. You can now:. * Turn on the display of IX Route Servers,.* Quickly hide your own sessions, .* Switch between straight lines and bendy ones.

And finally, as always a load of smaller fixes/improvements,. 🧵4/4. ---. You can see the full change log here:.

3. Super Looking Glass Improvements. You can now invert the ASN filter on the super looking glass, in addition the site now displays the number of paths that were not shown due to the sessions being flagged as not for public export. 🧵3/4

2. RPKI History Search. Want to know the history of RPKI ROA? Ask no more, now has a RPKI history search function from 2015 to today. 🧵2/4

The April 2024 changelog is out!. Major changes include:. 1. Forward DNS History. See what IPs _used_ to point into a IP block, or find out when a Domain started being served from a IP block. 🧵1/4

Has 2000::/12 been announced again?. Not yet!. But that did not stop GTT / AS3257 from carrying such a mistake.

Small improvement to the looking glass!. You can now invert the search, and you can also see how many matching paths were "hidden" due to the feeds export settings

Find it here: , or by using the [History] link on the Validation tab for IP Prefixes

New feature: RPKI ROA History Search!. Allows you to search the RPKI ROA entries of the past, or to give you extra context of previous uses of a IP block. It was super useful when investigating the Orange Spain RPKI Incident