bgpreport

Network · data from 2026-11-12

AS26407 CAROLINA-DIGITAL-PHONE - Carolina Digital Phone, Inc.

Registry name: CAROLINA-DIGITAL-PHONE - Carolina Digital Phone, Inc., US · not in PeeringDB

8IPv4 routes 62.5% RPKI valid · 87.5% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
3No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS26407, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS26407, 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.
199.58.104.0/22 No ROA None 673 100% 67
66.248.128.0/19 No ROA Other IRR onlyRADB 673 100% 67
208.53.0.0/19 No ROA Other IRR onlyRADB 673 100% 67
64.6.172.0/24 Valid RIR databaseARIN, RADB 673 100% 67
64.6.173.0/24 Valid RIR databaseARIN, RADB 673 100% 67
64.81.190.0/24 Valid RIR databaseARIN, RADB 673 100% 67
178.92.81.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
64.81.178.0/24 Valid RIR databaseARIN, RADB 664 99% 67

AS-SET

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

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none199.58.104.0/22No ROA covers it. Add a ROA for AS26407, maxLength 22.673 of 673
Route object: none199.58.104.0/22No route object for it. Add a route object with origin AS26407 in the RIR database for the space.673 of 673
ROA: none66.248.128.0/19No ROA covers it. Add a ROA for AS26407, maxLength 19.673 of 673
Route object: RIR66.248.128.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none208.53.0.0/19No ROA covers it. Add a ROA for AS26407, maxLength 19.673 of 673
Route object: RIR208.53.0.0/19Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

67.218.224.0/19RADBNo ROA
74.85.90.0/23ARINValid
208.53.3.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.