bgpreport

Network · data from 2026-11-12

AS263665

Not in the RIR AS name list · not in PeeringDB

8IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
1Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS263665, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263665, 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.227.188.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
45.227.190.0/23 Valid Other IRR onlyRADB, TC 672 100% 66
131.161.108.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
138.255.172.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
168.196.20.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
170.150.112.0/22 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
191.241.32.0/21 Valid Other IRR onlyALTDB, RADB, TC 669 99% 66
2804:1134::/32 Valid Other IRR onlyRADB, TC 633 100% 67
2804:343c::/32 Valid Other IRR onlyALTDB, RADB, TC 633 100% 67
2804:47c0::/32 Valid Other IRR onlyALTDB, RADB, TC 633 100% 67
45.227.188.0/22 Valid Other IRR onlyALTDB, RADB, TC 66 10%low visibility 33

AS-SET

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

  • Route object: RIR11
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR45.227.188.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.227.190.0/23Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR131.161.108.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR138.255.172.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR168.196.20.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.150.112.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR191.241.32.0/21Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:1134::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:343c::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:47c0::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.633 of 636
Route object: RIR45.227.188.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.66 of 673

Route objects not announced

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

168.121.25.0/24RADBNo ROA
170.150.204.0/22RADBValid

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.