bgpreport

Network · data from 2026-11-12

AS28094 Southern Cable Network

Registry name: AS28094 - Southern Cable Network, BZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28094, 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.
176.53.184.0/23 No ROA Other IRR onlyRADB 671 100% 67
190.242.32.0/22 Valid None 670 100% 67
131.161.148.0/22 Valid Other IRR onlyRADB 671 100% 67
200.123.208.0/21 Valid Other IRR onlyRADB 670 100% 67
2803:7900::/32 Valid Other IRR onlyRADB 634 100% 68
2803:7900::/34 Valid Other IRR onlyRADB 634 100% 68
2803:7900:4000::/34 Valid Other IRR onlyRADB 633 100% 68
2803:7900:8000::/34 Valid Other IRR onlyRADB 633 100% 68
2803:7900:c000::/34 Valid Other IRR onlyRADB 633 100% 68

AS-SET

AS28094'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 25 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR8
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none176.53.184.0/23No ROA covers it. Add a ROA for AS28094, maxLength 23.671 of 673
Route object: RIR176.53.184.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none190.242.32.0/22No route object for it. Add a route object with origin AS28094 in the RIR database for the space.670 of 673
Route object: RIR131.161.148.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.123.208.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2803:7900::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2803:7900::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2803:7900:4000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2803:7900:8000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2803:7900:c000::/34Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

177.238.96.0/20RADBNo ROA
177.238.112.0/20RADBNo ROA
177.239.48.0/20RADBNo ROA
177.239.64.0/20RADBNo ROA
187.252.144.0/21RADBNo ROA
187.252.156.0/22RADBNo ROA
187.253.192.0/21RADBNo ROA
189.214.252.0/22RADBNo ROA
189.215.216.0/21RADBNo ROA
189.220.228.0/23RADBNo ROA
189.220.240.0/21RADBNo ROA
189.221.208.0/21RADBNo ROA
189.221.235.0/24RADBNo ROA
201.160.100.0/22RADBNo ROA
201.160.160.0/20RADBNo 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.