bgpreport

Network · data from 2026-11-12

AS211087

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS211087, 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.
2a13:9500:1bf::/48 Valid None 613 96% 67
2a0c:9a40:8f80::/48 Valid Other IRR onlyALTDB 635 100% 67

AS-SET

AS211087 isn't in PeeringDB, where networks name their 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 4 are in fix.csv.

  • Route object: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none2a13:9500:1bf::/48No route object for it. Add a route object with origin AS211087 in the RIR database for the space.613 of 636
Route object: RIR2a0c:9a40:8f80::/48Route object only in ALTDB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

2804:77cc:fffe::/48ALTDBInvalid: origin
2804:77cc:ffff::/48ALTDBInvalid: origin

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.