bgpreport

Network · data from 2026-11-12

AS400859 EXO-BROADBAND - EXO BROADBAND

Registry name: EXO-BROADBAND - EXO BROADBAND, US · not in PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
12Route objects not announced registered with origin AS400859, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS400859, 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.
199.7.149.0/24 Valid RIR databaseARIN 672 100% 67
16.220.152.0/24 Valid RIR databaseARIN, RADB 670 100% 67
16.220.156.0/24 Valid RIR databaseARIN, RADB 670 100% 67
16.220.155.0/24 Valid RIR databaseARIN, RADB 668 99% 67
16.220.153.0/24 Valid RIR databaseARIN, RADB 667 99% 67
199.7.151.0/24 Valid RIR databaseARIN 667 99% 67

AS-SET

AS400859 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 12 are in fix.csv.

  • Route object: not announced12

Route objects not announced

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

16.220.154.0/24ARIN, RADBValid
16.220.157.0/24ARINValid
16.220.158.0/24ARINValid
23.187.40.0/24ARINInvalid: origin
23.188.216.0/24ARINInvalid: origin
23.189.104.0/24ARINInvalid: origin
23.189.248.0/24ARINInvalid: origin
38.83.8.0/22RADBNo ROA
102.129.166.0/24AFRINICInvalid: origin
141.195.115.0/24ARINInvalid: origin
206.212.252.0/24ARINNo ROA
2602:fad4:43::/48ARIN, RADBValid

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.