bgpreport

Network · data from 2026-11-12

AS6372 DCANET - DCANet

Registry name: DCANET - DCANet, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS6372, 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.

216.158.48.0/24 No ROA Other origin onlycovered by 216.158.0.0/18 673 100% 67
207.245.64.0/18 No ROA Other IRR onlyRADB 673 100% 67
216.158.0.0/18 No ROA Other IRR onlyRADB 673 100% 67
2607:a4c0::/32 No ROA Other IRR onlyRADB 635 100% 68
204.183.80.0/20 No ROA Other IRR onlyRADB 156 23% 38
206.105.176.0/20 No ROA Other IRR onlyRADB 156 23% 38
208.0.32.0/20 No ROA Other IRR onlyRADB 156 23% 38
208.0.80.0/20 No ROA Other IRR onlyRADB 156 23% 38

AS-SET

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

  • ROA: none8
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none216.158.48.0/24No ROA covers it. Add a ROA for AS6372, maxLength 24.673 of 673
Route object: none216.158.48.0/24Route objects for it name AS46887. A route object for 216.158.0.0/18 with origin AS6372 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6372 in the RIR database for the space.673 of 673
ROA: none207.245.64.0/18No ROA covers it. Add a ROA for AS6372, maxLength 18.673 of 673
Route object: RIR207.245.64.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.158.0.0/18No ROA covers it. Add a ROA for AS6372, maxLength 18.673 of 673
Route object: RIR216.158.0.0/18Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2607:a4c0::/32No ROA covers it. Add a ROA for AS6372, maxLength 32.635 of 636
Route object: RIR2607:a4c0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none204.183.80.0/20No ROA covers it. Add a ROA for AS6372, maxLength 20.156 of 673
Route object: RIR204.183.80.0/20Route object only in RADB. Add it in the RIR database for the space.156 of 673
ROA: none206.105.176.0/20No ROA covers it. Add a ROA for AS6372, maxLength 20.156 of 673
Route object: RIR206.105.176.0/20Route object only in RADB. Add it in the RIR database for the space.156 of 673
ROA: none208.0.32.0/20No ROA covers it. Add a ROA for AS6372, maxLength 20.156 of 673
Route object: RIR208.0.32.0/20Route object only in RADB. Add it in the RIR database for the space.156 of 673
ROA: none208.0.80.0/20No ROA covers it. Add a ROA for AS6372, maxLength 20.156 of 673
Route object: RIR208.0.80.0/20Route object only in RADB. Add it in the RIR database for the space.156 of 673

Route objects not announced

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

66.59.192.0/24RADBNo ROA
67.17.251.0/24RADBNo ROA
165.160.0.0/16RADBNo ROA
198.137.254.0/24RADBNo ROA
198.178.249.0/24RADBNo ROA
198.178.250.0/24RADBNo ROA
198.178.251.0/24RADBNo ROA
199.4.189.0/24RADBNo ROA
204.75.178.0/24RADBNo ROA
204.90.71.0/24RADBNo ROA
207.122.127.0/24RADBNo ROA
2602:fa20::/40RADBNo 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.