bgpreport

Network · data from 2026-11-12

AS33067 CLASSICSOUTHCOMM

Registry name: CLASSICSOUTHCOMM - Classic South Communications, L.L.C., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33067, 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.
137.119.136.0/22 Valid Nonecovered by 137.119.136.0/21 671 100% 67
137.119.140.0/22 Valid Nonecovered by 137.119.136.0/21 671 100% 67
65.182.134.0/23 Valid RIR databaseARIN 671 100% 68
65.182.136.0/21 Valid RIR databaseARIN 671 100% 68
173.233.176.0/21 Valid RIR databaseARIN, RADB 671 100% 68
173.233.184.0/21 Valid RIR databaseARIN, RADB 671 100% 68
65.182.128.0/20 Valid RIR databaseARIN, RADB 667 99% 68
65.182.128.0/21 Valid RIR databaseARIN 667 99% 68
74.51.97.0/24 Valid RIR databaseARIN, RADB 667 99% 68
74.51.112.0/24 Valid RIR databaseARIN, RADB 667 99% 68
137.119.136.0/21 Valid RIR databaseARIN, RADB 667 99% 68
173.233.176.0/20 Valid RIR databaseARIN, RADB 667 99% 68

AS-SET

AS33067'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 4 are in fix.csv.

  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
Route object: none137.119.136.0/22No route object for it. A route object for 137.119.136.0/21 with origin AS33067 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33067 in the RIR database for the space.671 of 673
Route object: none137.119.140.0/22No route object for it. A route object for 137.119.136.0/21 with origin AS33067 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33067 in the RIR database for the space.671 of 673

Route objects not announced

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

64.53.24.0/24BBOINo ROA
207.144.135.0/24BBOINo 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.