bgpreport

Network · data from 2026-11-12

AS268108 UP INTERNET TELECOMUNICAÇÕES LTDA

Registry name: AS268108 - UP INTERNET TELECOMUNICACOES LTDA, BR · PeeringDB

7IPv4 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
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS268108, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS268108, 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.169.124.0/22 Valid Other IRR onlyRADB, TC 671 100% 67
45.169.124.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
45.169.126.0/23 Valid Other IRR onlyRADB, TC 671 100% 67
45.169.124.0/24 Valid Other IRR onlyRADB, TC 666 99% 67
2804:5820::/33 Valid Other IRR onlyTC 636 100% 67
2804:5820:8000::/33 Valid Other IRR onlyTC 636 100% 67
2804:5820::/32 Valid Other IRR onlyRADB, TC 635 100% 69
45.169.125.0/24 Valid Other IRR onlyRADB, TC 114 17% 41
45.169.126.0/24 Valid Other IRR onlyRADB, TC 114 17% 41
45.169.127.0/24 Valid Other IRR onlyRADB 114 17% 41

AS-SET

AS268108'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 22 are in fix.csv.

  • Route object: RIR10
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: RIR45.169.124.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.169.124.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.169.126.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.169.124.0/24Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
Route object: RIR2804:5820::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:5820:8000::/33Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:5820::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR45.169.125.0/24Route object only in RADB, TC. Add it in the RIR database for the space.114 of 673
Route object: RIR45.169.126.0/24Route object only in RADB, TC. Add it in the RIR database for the space.114 of 673
Route object: RIR45.169.127.0/24Route object only in RADB. Add it in the RIR database for the space.114 of 673

Route objects not announced

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

2804:5820::/34TCValid
2804:5820::/35TCValid
2804:5820:2000::/35TCValid
2804:5820:4000::/34TCValid
2804:5820:4000::/35TCValid
2804:5820:6000::/35TCValid
2804:5820:8000::/34TCValid
2804:5820:8000::/35TCValid
2804:5820:a000::/35TCValid
2804:5820:c000::/34TCValid
2804:5820:c000::/35TCValid
2804:5820:e000::/35TCValid

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.