bgpreport

Network · data from 2026-11-12

AS26616 AS26616 - Ubx Datacenter e Telecomunicacoes LTDA

Registry name: AS26616 - Ubx Datacenter e Telecomunicacoes LTDA, BR · not in PeeringDB

47IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
8Route objects not announced registered with origin AS26616, seen from no peer

Announced routes

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

200.152.48.0/24 Valid Other IRR onlyRADB 670 100% 67
200.229.166.0/24 Valid Other IRR onlyRADB 670 100% 67
200.152.62.0/24 Valid Other IRR onlyRADB 669 99% 67
200.152.48.0/23 Valid Other IRR onlyRADB 668 99% 67
200.152.49.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.50.0/23 Valid Other IRR onlyRADB 668 99% 67
200.152.50.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.51.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.52.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.53.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.54.0/23 Valid Other IRR onlyRADB 668 99% 67
200.152.54.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.55.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.56.0/21 Valid Other IRR onlyRADB 668 99% 67
200.152.56.0/23 Valid Other IRR onlyRADB 668 99% 67
200.152.56.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.57.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.58.0/23 Valid Other IRR onlyRADB 668 99% 67
200.152.58.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.59.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.60.0/23 Valid Other IRR onlyRADB 668 99% 67
200.152.60.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.61.0/24 Valid Other IRR onlyRADB 668 99% 67
200.152.62.0/23 Valid Other IRR onlyRADB 668 99% 67
200.152.63.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.160.0/21 Valid Other IRR onlyRADB 668 99% 67
200.229.160.0/22 Valid Other IRR onlyRADB 668 99% 67
200.229.160.0/23 Valid Other IRR onlyRADB 668 99% 67
200.229.160.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.161.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.162.0/23 Valid Other IRR onlyRADB 668 99% 67
200.229.162.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.163.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.164.0/22 Valid Other IRR onlyRADB 668 99% 67
200.229.164.0/23 Valid Other IRR onlyRADB 668 99% 67
200.229.164.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.165.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.166.0/23 Valid Other IRR onlyRADB 668 99% 67
200.229.167.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.168.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.170.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.172.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.173.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.174.0/23 Valid Other IRR onlyRADB 668 99% 67
200.229.174.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.175.0/24 Valid Other IRR onlyRADB 668 99% 67
200.229.169.0/24 Valid Other IRR onlyRADB 663 99% 67

AS-SET

AS26616 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 55 are in fix.csv.

  • Route object: RIR47
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR200.152.48.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR200.229.166.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR200.152.62.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.152.48.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.49.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.50.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.50.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.51.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.52.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.53.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.54.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.54.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.55.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.56.0/21Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.56.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.56.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.57.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.58.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.58.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.59.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.60.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.60.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.61.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.62.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.152.63.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.160.0/21Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.160.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.160.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.160.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.161.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.162.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.162.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.163.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.164.0/22Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.164.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.164.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.165.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.166.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.167.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.168.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.170.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.172.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.173.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.174.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.174.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.175.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.229.169.0/24Route object only in RADB. Add it in the RIR database for the space.663 of 673

Route objects not announced

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

200.152.48.0/20RADBValid
200.152.48.0/21RADBValid
200.152.52.0/22RADBValid
200.152.52.0/23RADBValid
200.229.160.0/20RADBValid
200.229.168.0/23RADBValid
200.229.171.0/24RADBValid
2804:3fe4::/32RADBValid

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.