bgpreport

Network · data from 2026-11-12

AS395974 COMCAST-MES - Comcast Cable Communications, LLC

Registry name: COMCAST-MES - Comcast Cable Communications, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS395974, 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.
50.175.118.0/24 Valid Other origin only 2 0%low visibility 2
50.225.246.0/24 Valid RIR databaseARIN 664 99% 67

AS-SET

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

  • Route object: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none50.175.118.0/24Route objects for it name AS396017, AS396021. Add a route object with origin AS395974 in the RIR database for the space.2 of 673

Route objects not announced

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

96.114.45.160/27ARINValid
2001:558:feed:df::/64ARINValid
2001:55d:8069::/48ARINValid

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.