bgpreport

Network · data from 2026-11-12

AS30230 CONTINENT8-CLOUD - Continent 8 LLC

Registry name: CONTINENT8-CLOUD - Continent 8 LLC, US · not in PeeringDB

6IPv4 routes 100.0% RPKI valid · 66.7% 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
5Route objects not announced registered with origin AS30230, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS30230, 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.
66.84.66.0/24 Valid Other origin only 673 100% 66
109.202.113.0/24 Valid Other origin only 673 100% 66
66.84.67.0/24 Valid RIR databaseRIPE 673 100% 66
103.81.130.0/24 Valid RIR databaseAPNIC 673 100% 67
193.31.222.0/24 Valid RIR databaseRIPE 673 100% 66
66.212.231.0/24 Valid RIR databaseARIN 669 99% 67

AS-SET

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

  • Route object: none2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none66.84.66.0/24Route objects for it name AS14537. Add a route object with origin AS30230 in the RIR database for the space.673 of 673
Route object: none109.202.113.0/24Route objects for it name AS14537. Add a route object with origin AS30230 in the RIR database for the space.673 of 673

Route objects not announced

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

66.212.255.0/24ARINValid
68.169.224.0/21RADBNo ROA
68.169.232.0/22RADBNo ROA
68.169.236.0/23RADBNo ROA
216.168.208.0/24RADBNo 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.