AwanCerahBGP
Autonomous System

Comcast Cable Communications, LLC

AS33656United StatesARIN · since 2005Cable/DSL/ISPPeering: Restrictive

CMCS

C61/100Fair

BGP report

Ranked 7,548 of 19,165 networks in United States, 1,437 of 2,089 ISPs and transit networks. World rank 54,663.

  • RPKI ROA30/30
  • IRR route objects3/20
  • Upstream redundancy7/15
  • Global visibility1/10
  • IPv610/10
  • PeeringDB5/10
  • Prefix aggregation5/5

Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored

Score history

RPKI ROA

Good
30/30

64 of 64 prefixes have a matching ROA (valid). 0 without a ROA.

Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.

IRR route objects

Problem
3/20

9 prefixes have an exact route object, 0 are covered by a larger one, 55 only have objects with another origin, 0 have none.

Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.

How to fix
  1. Create route (IPv4) and route6 (IPv6) objects with your AS as origin in your RIR's IRR (for example APNIC via MyAPNIC, or IDNIC), or in RADB.
  2. Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
Route object with another origin (55)

Upstream redundancy

Problem
7/15

1 upstream, 0 peer, 1 downstream.

With a single upstream, any outage there cuts your whole network off the internet.

How to fix
  1. Add a second upstream from a different provider, and join an IXP to peer directly with other networks.
Upstream (1)

IPv6

Good
10/10

13 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
5/10

Profile exists. Missing: IRR as-set, IX connections, prefix counts.

Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.

How to fix
  1. Create or complete your profile at peeringdb.com: IRR as-set, peering policy, expected IPv4 and IPv6 prefix counts, and IX connections.

Prefix aggregation

Good
5/5

51 IPv4 prefixes could be summarized into 50.

Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.

Dropping invalid routes (ROV)

Good

Not seen passing on RPKI-invalid routes of other networks in sampled paths.

Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.

Put the badge on your website

BGP report AS33656The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS33656/rapor"><img src="https://bgp.awancerah.cloud/en/AS33656/rapor.svg" alt="BGP report AS33656"></a>
Markdown
[![BGP report AS33656](https://bgp.awancerah.cloud/en/AS33656/rapor.svg)](https://bgp.awancerah.cloud/en/AS33656/rapor)