bgpreport

Network · data from 2026-11-12

AS401299 SIPNAV-EAST - SipNav LLC

Registry name: SIPNAV-EAST - SipNav LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401299, 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.

2606:92c0:1600::/40 No ROA Other IRR onlyRADB 633 100% 69
2606:92c0:ff00::/40 No ROA Other IRR onlyRADB 403 63% 53
88.151.132.0/24 No ROA RIR databaseARIN 670 100% 68
88.151.133.0/24 No ROA RIR databaseARIN 670 100% 68
88.151.134.0/24 No ROA RIR databaseARIN, RADB 666 99% 68
66.96.95.0/24 Valid Other origin only 670 100% 68

AS-SET

AS401299 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 9 are in fix.csv.

  • ROA: none5
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2606:92c0:1600::/40No ROA covers it. Add a ROA for AS401299, maxLength 40.633 of 636
Route object: RIR2606:92c0:1600::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2606:92c0:ff00::/40No ROA covers it. Add a ROA for AS401299, maxLength 40.403 of 636
Route object: RIR2606:92c0:ff00::/40Route object only in RADB. Add it in the RIR database for the space.403 of 636
ROA: none88.151.132.0/24No ROA covers it. Add a ROA for AS401299, maxLength 24.670 of 673
ROA: none88.151.133.0/24No ROA covers it. Add a ROA for AS401299, maxLength 24.670 of 673
ROA: none88.151.134.0/24No ROA covers it. Add a ROA for AS401299, maxLength 24.666 of 673
Route object: none66.96.95.0/24Route objects for it name AS29802. Add a route object with origin AS401299 in the RIR database for the space.670 of 673

Route objects not announced

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

88.151.135.0/24ARINNo 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.