bgpreport

Network · data from 2026-11-12

AS273277 SUPER CABLE DEL SURESTE

Registry name: AS273277 - SUPER CABLE DEL SURESTE, MX · PeeringDB

2IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
6Route objects not announced registered with origin AS273277, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS273277, 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.189.104.0/22 No ROA Other IRR onlyRADB 673 100% 67
45.189.107.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS273277'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 10 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none45.189.104.0/22No ROA covers it. Add a ROA for AS273277, maxLength 22.673 of 673
Route object: RIR45.189.104.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none45.189.107.0/24No ROA covers it. Add a ROA for AS273277, maxLength 24.672 of 673
Route object: RIR45.189.107.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

45.189.104.0/23RADBNo ROA
45.189.104.0/24RADBNo ROA
45.189.105.0/24RADBNo ROA
45.189.106.0/23RADBNo ROA
45.189.106.0/24RADBNo ROA
2806:442::/32RADBNo 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.