bgpreport

Network · data from 2026-11-12

AS266573 MVSONET

Registry name: AS266573 - UPLINK TELECOM, BR · PeeringDB

7IPv4 routes 0.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
8No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS266573, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266573, 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.7.112.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
45.7.112.0/23 No ROA Other IRR onlyTC 670 100% 67
45.7.114.0/23 No ROA Other IRR onlyRADB, TC 670 100% 67
2804:3e18::/32 No ROA Other IRR onlyRADB, TC 632 99% 67
45.7.112.0/24 No ROA Other IRR onlyRADB, TC 136 20% 45
45.7.113.0/24 No ROA Other IRR onlyRADB, TC 136 20% 45
45.7.114.0/24 No ROA Other IRR onlyRADB, TC 136 20% 45
45.7.115.0/24 No ROA Other IRR onlyRADB, TC 136 20% 45

AS-SET

AS266573'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 30 are in fix.csv.

  • ROA: none8
  • Route object: RIR8
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none45.7.112.0/22No ROA covers it. Add a ROA for AS266573, maxLength 22.671 of 673
Route object: RIR45.7.112.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none45.7.112.0/23No ROA covers it. Add a ROA for AS266573, maxLength 23.670 of 673
Route object: RIR45.7.112.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none45.7.114.0/23No ROA covers it. Add a ROA for AS266573, maxLength 23.670 of 673
Route object: RIR45.7.114.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:3e18::/32No ROA covers it. Add a ROA for AS266573, maxLength 32.632 of 636
Route object: RIR2804:3e18::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
ROA: none45.7.112.0/24No ROA covers it. Add a ROA for AS266573, maxLength 24.136 of 673
Route object: RIR45.7.112.0/24Route object only in RADB, TC. Add it in the RIR database for the space.136 of 673
ROA: none45.7.113.0/24No ROA covers it. Add a ROA for AS266573, maxLength 24.136 of 673
Route object: RIR45.7.113.0/24Route object only in RADB, TC. Add it in the RIR database for the space.136 of 673
ROA: none45.7.114.0/24No ROA covers it. Add a ROA for AS266573, maxLength 24.136 of 673
Route object: RIR45.7.114.0/24Route object only in RADB, TC. Add it in the RIR database for the space.136 of 673
ROA: none45.7.115.0/24No ROA covers it. Add a ROA for AS266573, maxLength 24.136 of 673
Route object: RIR45.7.115.0/24Route object only in RADB, TC. Add it in the RIR database for the space.136 of 673

Route objects not announced

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

2804:3e18::/33TCNo ROA
2804:3e18::/34TCNo ROA
2804:3e18::/35TCNo ROA
2804:3e18:2000::/35TCNo ROA
2804:3e18:4000::/34TCNo ROA
2804:3e18:4000::/35TCNo ROA
2804:3e18:6000::/35TCNo ROA
2804:3e18:8000::/33TCNo ROA
2804:3e18:8000::/34TCNo ROA
2804:3e18:8000::/35TCNo ROA
2804:3e18:a000::/35TCNo ROA
2804:3e18:c000::/34TCNo ROA
2804:3e18:c000::/35TCNo ROA
2804:3e18:e000::/35TCNo ROA

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.