bgpreport

Network · data from 2026-11-12

AS36733 DNEO-OSP7 - Comcast Cable Communications, LLC

Registry name: DNEO-OSP7 - Comcast Cable Communications, LLC, US · not in PeeringDB

30IPv4 routes 100.0% RPKI valid · 100.0% with a route object
20IPv6 routes 75.0% RPKI valid · 75.0% with a route object
5RPKI invalid 5 origin · 0 maxLength
0No ROA 5 with no route object for this origin
50Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS36733, seen from no peer

Announced routes

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

2001:558:601b::/48 Invalid: origin None 3 0%low visibility 1
2601:b40::/26 Invalid: origin None 3 0%low visibility 1
2601:b40:100::/40 Invalid: origin None 3 0%low visibility 1
2603:2f80::/26 Invalid: origin None 3 0%low visibility 1
2603:2f80:100::/40 Invalid: origin None 3 0%low visibility 1
67.174.80.0/20 Valid RIR databaseARIN 5 1%low visibility 3
68.85.136.0/23 Valid RIR databaseARIN 5 1%low visibility 3
68.85.215.0/24 Valid RIR databaseARIN 5 1%low visibility 3
68.86.134.0/23 Valid RIR databaseARIN 5 1%low visibility 3
68.86.228.0/23 Valid RIR databaseARIN 5 1%low visibility 3
68.87.16.0/22 Valid RIR databaseARIN 5 1%low visibility 3
68.87.24.0/24 Valid RIR databaseARIN 5 1%low visibility 3
68.87.26.0/23 Valid RIR databaseARIN 5 1%low visibility 3
68.87.28.0/22 Valid RIR databaseARIN 5 1%low visibility 3
68.87.32.0/20 Valid RIR databaseARIN 5 1%low visibility 3
68.87.96.0/20 Valid RIR databaseARIN 5 1%low visibility 3
69.139.191.0/24 Valid RIR databaseARIN 5 1%low visibility 3
69.139.244.0/23 Valid RIR databaseARIN 5 1%low visibility 3
69.241.18.0/23 Valid RIR databaseARIN 5 1%low visibility 3
69.241.40.0/21 Valid RIR databaseARIN 5 1%low visibility 3
69.241.72.0/24 Valid RIR databaseARIN 5 1%low visibility 3
69.247.96.0/20 Valid RIR databaseARIN 5 1%low visibility 3
75.149.106.0/23 Valid RIR databaseARIN 5 1%low visibility 3
76.26.112.0/21 Valid RIR databaseARIN 5 1%low visibility 3
76.96.48.0/20 Valid RIR databaseARIN 5 1%low visibility 3
76.96.64.0/20 Valid RIR databaseARIN 5 1%low visibility 3
96.82.16.0/23 Valid RIR databaseARIN 5 1%low visibility 3
96.108.38.0/23 Valid RIR databaseARIN 5 1%low visibility 3
96.108.76.0/22 Valid RIR databaseARIN 5 1%low visibility 3
96.108.144.0/23 Valid RIR databaseARIN 5 1%low visibility 3
96.115.158.0/23 Valid RIR databaseARIN 5 1%low visibility 3
96.116.0.0/19 Valid RIR databaseARIN 5 1%low visibility 3
96.119.96.0/19 Valid RIR databaseARIN 5 1%low visibility 3
162.150.160.0/20 Valid RIR databaseARIN 5 1%low visibility 3
2001:558:e0::/44 Valid RIR databaseARIN 5 1%low visibility 3
2001:558:400::/44 Valid RIR databaseARIN 5 1%low visibility 3
2001:558:502a::/48 Valid RIR databaseARIN 5 1%low visibility 3
2001:558:6000::/48 Valid RIR databaseARIN 5 1%low visibility 3
2001:558:fc0b::/48 Valid RIR databaseARIN 5 1%low visibility 3
2001:558:fe14::/48 Valid RIR databaseARIN 5 1%low visibility 3
2001:558:ff00::/40 Valid RIR databaseARIN 5 1%low visibility 3
2601:a40::/26 Valid RIR databaseARIN 5 1%low visibility 3
2601:a40:202::/48 Valid RIR databaseARIN 5 1%low visibility 3
2601:a40:600::/40 Valid RIR databaseARIN 5 1%low visibility 3
2601:a40:700::/40 Valid RIR databaseARIN 5 1%low visibility 3
2603:2a40::/26 Valid RIR databaseARIN 5 1%low visibility 3
2603:2a40:5::/48 Valid RIR databaseARIN 5 1%low visibility 3
2603:2a40:600::/40 Valid RIR databaseARIN 5 1%low visibility 3
2603:3019::/32 Valid RIR databaseARIN 5 1%low visibility 3
73.5.240.0/20 Valid RIR databaseARIN 3 0%low visibility 1

AS-SET

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

  • ROA: origin5
  • Route object: none5
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: origin2001:558:601b::/48ROAs covering it name AS7922, not AS36733. If AS36733 should announce it, add a ROA for AS36733.3 of 636
Route object: none2001:558:601b::/48No route object for it. Add a route object with origin AS36733 in the RIR database for the space.3 of 636
ROA: origin2601:b40::/26ROAs covering it name AS7922, not AS36733. If AS36733 should announce it, add a ROA for AS36733.3 of 636
Route object: none2601:b40::/26No route object for it. Add a route object with origin AS36733 in the RIR database for the space.3 of 636
ROA: origin2601:b40:100::/40ROAs covering it name AS7922, not AS36733. If AS36733 should announce it, add a ROA for AS36733.3 of 636
Route object: none2601:b40:100::/40No route object for it. Add a route object with origin AS36733 in the RIR database for the space.3 of 636
ROA: origin2603:2f80::/26ROAs covering it name AS7922, not AS36733. If AS36733 should announce it, add a ROA for AS36733.3 of 636
Route object: none2603:2f80::/26No route object for it. Add a route object with origin AS36733 in the RIR database for the space.3 of 636
ROA: origin2603:2f80:100::/40ROAs covering it name AS7922, not AS36733. If AS36733 should announce it, add a ROA for AS36733.3 of 636
Route object: none2603:2f80:100::/40No route object for it. Add a route object with origin AS36733 in the RIR database for the space.3 of 636

Route objects not announced

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

64.235.160.0/19ARINValid
65.97.0.0/20ARINValid
65.97.16.0/20ARINValid
68.81.10.0/23ARINValid
69.137.133.0/24ARINValid
96.97.20.0/22ARINValid
96.109.130.0/23ARINValid
96.216.36.0/22ARINValid
98.40.34.0/23ARINValid
2001:558:460::/44ARINValid
2001:558:461::/48ARINValid
2001:558:fee7::/48ARINValid
2001:df4:2a00::/48APNICValid

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.