AwanCerahBGP
Autonomous System

Comcast Cable Communications, LLC

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

CMCS

B77/100Good

BGP report

Ranked 4,496 of 19,166 networks in United States. World rank 33,211.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy7/15
  • Global visibility0/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

54 of 54 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

Needs work
20/20

53 prefixes have an exact route object, 0 are covered by a larger one, 1 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 (1)

Upstream redundancy

Problem
7/15

1 upstream, 0 peer, 0 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

6 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

48 IPv4 prefixes could be summarized into 46.

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

Put the badge on your website

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