bgpreport

Network · data from 2026-11-12

AS201497 express-as STAT EXPRESS SERVICES LTD

Registry name: express-as STAT EXPRESS SERVICES LTD, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201497, 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.
2001:678:c18::/48 No ROA RIR databaseRIPE 632 99% 69
91.194.194.0/23 Valid RIR databaseRIPE 673 100% 67
2.57.152.0/22 Valid RIR databaseRIPE 671 100% 68
2.59.204.0/22 Valid RIR databaseRIPE 671 100% 68
45.150.44.0/22 Valid RIR databaseRIPE 671 100% 68
171.22.52.0/22 Valid RIR databaseRIPE 671 100% 68
194.50.184.0/23 Valid RIR databaseRIPE 671 100% 68
194.50.188.0/23 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS201497 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.

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none2001:678:c18::/48No ROA covers it. Add a ROA for AS201497, maxLength 48.632 of 636

Route objects not announced

Every route object with origin AS201497 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.