bgpreport

Network · data from 2026-11-12

AS209902 RAIWAY

Registry name: RAIWAY RAI WAY S.P.A., IT · PeeringDB

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

Announced routes

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

45.139.96.0/22 Valid RIR databaseRIPE 671 100% 66
45.139.96.0/23 Valid RIR databaseRIPE 671 100% 66
80.88.232.0/22 Valid RIR databaseRIPE 671 100% 66
185.91.68.0/24 Valid RIR databaseRIPE 671 100% 66
185.166.180.0/22 Valid RIR databaseRIPE 671 100% 66
185.243.204.0/22 Valid RIR databaseRIPE 671 100% 66
195.35.118.0/23 Valid RIR databaseRIPE 671 100% 66
195.211.165.0/24 Valid RIR databaseRIPE 671 100% 66
2a12:5140:1000::/36 Valid RIR databaseRIPE 634 100% 67
2a12:5140:2000::/36 Valid RIR databaseRIPE 634 100% 67
2a12:5140:101::/48 Valid RIR databaseRIPE 633 100% 67
2a12:5140:102::/48 Valid RIR databaseRIPE 633 100% 67
2a12:5140:105::/48 Valid RIR databaseRIPE 633 100% 67
2a12:5140:108::/48 Valid RIR databaseRIPE 633 100% 67
2a12:5140:109::/48 Valid RIR databaseRIPE 633 100% 67
2a12:5140:10a::/48 Valid RIR databaseRIPE 633 100% 67
2a12:5140:10b::/48 Valid RIR databaseRIPE 633 100% 67
2a12:5140:103::/48 Valid RIR databaseRIPE 630 99% 67
2a12:5140:1000::/40 Valid RIR databaseRIPE 328 52% 63
2a12:5140:1600::/40 Valid RIR databaseRIPE 328 52% 63
2a12:5140:2000::/40 Valid RIR databaseRIPE 326 51% 64
2a12:5140:5000::/36 Valid RIR databaseRIPE 318 50% 63
185.243.206.0/24 Valid RIR databaseRIPE 122 18% 39
185.243.204.0/24 Valid RIR databaseRIPE 105 16% 38
45.139.96.0/24 Valid RIR databaseRIPE 4 1%low visibility 7
45.139.97.0/24 Valid RIR databaseRIPE 4 1%low visibility 7
195.35.118.0/24 Valid RIR databaseRIPE 4 1%low visibility 7
195.35.119.0/24 Valid RIR databaseRIPE 4 1%low visibility 7
45.139.98.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
45.139.99.0/24 Valid RIR databaseRIPE 2 0%low visibility 3
2a12:5140:1040::/44 Valid RIR databaseRIPE 2 0%low visibility 2
2a12:5140:1640::/44 Valid RIR databaseRIPE 2 0%low visibility 2
2a12:5140:2040::/44 Valid RIR databaseRIPE 2 0%low visibility 3
80.88.232.0/24 Valid RIR databaseRIPE 0 0%low visibility 1
185.166.180.0/24 Valid RIR databaseRIPE 0 0%low visibility 1
185.166.181.0/24 Valid RIR databaseRIPE 0 0%low visibility 1
185.166.182.0/24 Valid RIR databaseRIPE 0 0%low visibility 1
185.166.183.0/24 Valid RIR databaseRIPE 0 0%low visibility 1
185.243.207.0/24 Valid RIR databaseRIPE 0 0%low visibility 1

AS-SET

AS209902's PeeringDB record names no 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 41 are in fix.csv.

  • Route object: not announced41

Route objects not announced

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

80.88.232.0/21RIPENo ROA
80.88.236.0/22RIPEInvalid: origin
2a12:5140::/29RIPENo ROA
2a12:5140:1400::/40RIPEValid
2a12:5140:1440::/44RIPEValid
2a12:5140:2400::/40RIPEValid
2a12:5140:2440::/44RIPEValid
2a12:5140:3000::/36RIPEValid
2a12:5140:3000::/40RIPEValid
2a12:5140:3040::/44RIPEValid
2a12:5140:3400::/40RIPEValid
2a12:5140:3440::/44RIPEValid
2a12:5140:4000::/36RIPEValid
2a12:5140:4000::/40RIPEValid
2a12:5140:4040::/44RIPEValid
2a12:5140:4800::/40RIPEValid
2a12:5140:4840::/44RIPEValid
2a12:5140:5000::/40RIPEValid
2a12:5140:5040::/44RIPEValid
2a12:5140:6000::/36RIPEValid
2a12:5140:6000::/40RIPEValid
2a12:5140:6040::/44RIPEValid
2a12:5140:7000::/36RIPEValid
2a12:5140:7000::/40RIPEValid
2a12:5140:7040::/44RIPEValid
2a12:5140:7800::/40RIPEValid
2a12:5140:7840::/44RIPEValid
2a12:5140:8000::/36RIPEValid
2a12:5140:8000::/40RIPEValid
2a12:5140:8040::/44RIPEValid
2a12:5144::/36RIPEValid
2a12:5144:2000::/36RIPEValid
2a12:5144:2200::/40RIPEValid
2a12:5144:3000::/36RIPEValid
2a12:5144:3000::/40RIPEValid
2a12:5144:3400::/40RIPEValid
2a12:5144:4000::/36RIPEValid
2a12:5144:4000::/40RIPEValid
2a12:5144:5000::/36RIPEValid
2a12:5144:5000::/40RIPEValid
2a12:5144:f000::/36RIPEValid

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.