bgpreport

Network · data from 2026-11-12

AS2008999

Not in the RIR AS name list · not in PeeringDB

AS2008999 is Unallocated in IANA's AS number registries. The routes below have it as their origin anyway, as seen by the collectors' peers.

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS2008999, 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.
31.7.168.0/24 No ROA Other origin only 109 16% 46
31.7.169.0/24 No ROA Other origin only 109 16% 46
31.7.170.0/24 No ROA Other origin only 109 16% 46
31.7.171.0/24 No ROA Other origin only 109 16% 46
31.7.173.0/24 No ROA Other origin only 109 16% 46
31.7.175.0/24 No ROA Other origin only 109 16% 46
93.95.64.0/24 No ROA Other origin only 108 16% 46
93.95.68.0/24 No ROA Other origin only 108 16% 46
93.95.69.0/24 No ROA Other origin only 108 16% 46
93.95.71.0/24 No ROA Other origin only 108 16% 46
185.64.84.0/24 No ROA Other origin only 108 16% 46
185.64.85.0/24 No ROA Other origin only 108 16% 46
185.64.86.0/24 No ROA Other origin only 108 16% 46
185.64.87.0/24 No ROA Other origin only 108 16% 46
185.229.24.0/24 No ROA Other origin only 101 15% 45
185.231.156.0/24 No ROA Other origin only 101 15% 45
185.250.252.0/24 No ROA Other origin only 101 15% 45
185.250.253.0/24 No ROA Other origin only 101 15% 45
185.250.254.0/24 No ROA Other origin only 101 15% 45
31.7.172.0/24 No ROA Other origin only 84 12% 40
31.7.174.0/24 No ROA Other origin only 84 12% 40
185.230.252.0/24 No ROA Other origin only 80 12% 40
185.230.253.0/24 No ROA Other origin only 80 12% 40
185.230.254.0/24 No ROA Other origin only 80 12% 40
185.230.255.0/24 No ROA Other origin only 80 12% 40

AS-SET

AS2008999 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 1 are in fix.csv.

  • Bogon origin1
ChangePrefix or setDetailFull-table peers
Bogon originAS2008999AS2008999 is Unallocated in IANA's AS number registries; 25 routes in the global table have it as their origin.

Route objects not announced

Every route object with origin AS2008999 is announced.

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.