bgpreport

Network · data from 2026-11-12

AS201612 TLD Box Anycast

Registry name: NICAT-MINICAST-AS nic.at GmbH, AT · PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
20Route objects not announced registered with origin AS201612, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201612, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

194.0.24.0/24 Valid RIR databaseALTDB, RADB, RIPE 673 100% 66
194.0.26.0/24 Valid RIR databaseALTDB, RIPE 671 100% 69
2001:67c:10e0::/48 Valid RIR databaseALTDB, RIPE 636 100% 70
2001:678:24::/48 Valid RIR databaseALTDB, RIPE 634 100% 69

AS-SET

AS201612's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 20 are in fix.csv.

  • Route object: not announced20

Route objects not announced

Route objects with origin AS201612 whose prefix no peer sees AS201612 announce. Many are kept on purpose (backup routes, space announced only in some places).

91.237.67.0/24RIPENo ROA
176.97.158.0/24ALTDB, RIPEValid
185.80.188.0/22RIPENo ROA
185.80.188.0/24RIPEValid
185.80.189.0/24RIPEValid
185.80.190.0/24RIPEValid
185.80.191.0/24RIPEValid
185.167.176.0/24RIPENo ROA
192.174.68.0/24ALTDB, RIPEValid
194.0.25.0/24ALTDB, RIPEValid
2001:678:20::/48ALTDB, RIPEValid
2001:67c:1bc::/48ALTDB, RIPEValid
2001:67c:10b8::/48ALTDB, RIPEValid
2a05:7f00::/29RIPENo ROA
2a05:7f00:188::/48RIPEValid
2a05:7f00:189::/48RIPEValid
2a05:7f00:190::/48RIPEValid
2a05:7f00:191::/48RIPEValid
2a0b:8e00::/48RIPENo ROA
2a0b:8e00:1::/48RIPENo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.