bgpreport

Network · data from 2026-11-12

AS267360 Uniacesso Serviços de Comunicação Multimidia

Registry name: AS267360 - Uniacesso Serv. Comunicacao Multimidia, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267360, 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.234.52.0/23 Valid Other IRR onlyTC 669 99% 67
45.234.54.0/24 Valid Other IRR onlyTC 669 99% 66
45.234.55.0/24 Valid Other IRR onlyTC 669 99% 67
45.234.52.0/24 Valid Other IRR onlyTC 667 99% 67
45.234.53.0/24 Valid Other IRR onlyTC 667 99% 67
2804:4c44::/32 Valid Other IRR onlyTC 633 100% 67
2804:4c44::/34 Valid Other IRR onlyTC 633 100% 67
2804:4c44:4000::/34 Valid Other IRR onlyTC 633 100% 67
2804:4c44:8000::/34 Valid Other IRR onlyTC 633 100% 67
2804:4c44:c000::/34 Valid Other IRR onlyTC 633 100% 67

AS-SET

AS267360'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 12 are in fix.csv.

  • Route object: RIR10
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: RIR45.234.52.0/23Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.234.54.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.234.55.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR45.234.52.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR45.234.53.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:4c44::/32Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4c44::/34Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4c44:4000::/34Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4c44:8000::/34Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:4c44:c000::/34Route object only in TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

45.234.52.0/22RADB, TCNo ROA
45.234.54.0/23TCNo 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.