bgpreport

Network · data from 2026-11-12

AS33176 DTCCAAS

Registry name: DTCCAAS - DTC Cable, US · PeeringDB

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

Announced routes

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

205.164.112.0/24 No ROA Nonecovered by 205.164.112.0/23 671 100% 67
205.164.113.0/24 No ROA Nonecovered by 205.164.112.0/23 671 100% 67
38.46.42.0/23 No ROA Other IRR onlyRADB 671 100% 67
38.57.152.0/23 No ROA Other IRR onlyRADB 671 100% 67
154.39.24.0/21 No ROA Other IRR onlyRADB 671 100% 67
204.14.56.0/21 No ROA Other IRR onlyRADB 671 100% 67
208.83.168.0/21 No ROA Other IRR onlyRADB 671 100% 67
2605:2500::/32 No ROA Other IRR onlyRADB 632 99% 68

AS-SET

AS33176'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 20 are in fix.csv.

  • ROA: none8
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none205.164.112.0/24No ROA covers it. Add a ROA for AS33176, maxLength 24.671 of 673
Route object: none205.164.112.0/24No route object for it. A route object for 205.164.112.0/23 with origin AS33176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33176 in the RIR database for the space.671 of 673
ROA: none205.164.113.0/24No ROA covers it. Add a ROA for AS33176, maxLength 24.671 of 673
Route object: none205.164.113.0/24No route object for it. A route object for 205.164.112.0/23 with origin AS33176 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33176 in the RIR database for the space.671 of 673
ROA: none38.46.42.0/23No ROA covers it. Add a ROA for AS33176, maxLength 23.671 of 673
Route object: RIR38.46.42.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.57.152.0/23No ROA covers it. Add a ROA for AS33176, maxLength 23.671 of 673
Route object: RIR38.57.152.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none154.39.24.0/21No ROA covers it. Add a ROA for AS33176, maxLength 21.671 of 673
Route object: RIR154.39.24.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none204.14.56.0/21No ROA covers it. Add a ROA for AS33176, maxLength 21.671 of 673
Route object: RIR204.14.56.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none208.83.168.0/21No ROA covers it. Add a ROA for AS33176, maxLength 21.671 of 673
Route object: RIR208.83.168.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2605:2500::/32No ROA covers it. Add a ROA for AS33176, maxLength 32.632 of 636
Route object: RIR2605:2500::/32Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

12.39.76.0/23ARINNo ROA
12.152.144.0/20ARINNo ROA
12.152.150.0/23RADBNo ROA
205.164.112.0/23RADBNo 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.