bgpreport

Network · data from 2026-11-12

AS400940 Railway

Registry name: RAILWAY - Railway, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS400940, 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.
2607:99c0:c00::/40 Valid None 636 100% 69
2607:99c0:800::/40 Valid None 635 100% 67
2607:99c0:900::/40 Valid None 635 100% 67
2607:99c0:a00::/40 Valid None 634 100% 68
66.33.22.0/23 Valid RIR databaseARIN 673 100% 67
66.33.23.0/24 Valid RIR databaseARIN 673 100% 70
152.55.176.0/22 Valid RIR databaseARIN 673 100% 67
152.55.180.0/22 Valid RIR databaseARIN 673 100% 67
152.55.184.0/22 Valid RIR databaseARIN 673 100% 67
152.55.188.0/22 Valid RIR databaseARIN 673 100% 67
162.220.232.0/23 Valid RIR databaseARIN 673 100% 67
162.220.234.0/23 Valid RIR databaseARIN 673 100% 67
208.77.244.0/23 Valid RIR databaseARIN 673 100% 67
153.52.224.0/23 Valid RIR databaseARIN 672 100% 67
208.77.246.0/23 Valid RIR databaseARIN 671 100% 67
69.46.46.0/24 Valid RIR databaseARIN 667 99% 66
153.52.255.0/24 Valid RIR databaseARIN 667 99% 66
2607:99c0:300::/40 Valid RIR databaseARIN 636 100% 68
2607:99c0::/40 Valid RIR databaseARIN 635 100% 67
2607:99c0:100::/40 Valid RIR databaseARIN 635 100% 67
2607:99c0:200::/40 Valid RIR databaseARIN 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS400940: AS-RLWY. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS400940 isn't in the set, or no route object for AS400940 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS400940 in itNot covered
AS-RLWY ARIN 2120 Yes 4

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

  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2607:99c0:c00::/40No route object for it. Add a route object with origin AS400940 in the RIR database for the space.636 of 636
Route object: none2607:99c0:800::/40No route object for it. Add a route object with origin AS400940 in the RIR database for the space.635 of 636
Route object: none2607:99c0:900::/40No route object for it. Add a route object with origin AS400940 in the RIR database for the space.635 of 636
Route object: none2607:99c0:a00::/40No route object for it. Add a route object with origin AS400940 in the RIR database for the space.634 of 636

Route objects not announced

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

66.33.22.0/24ARINValid

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.