Dialpad, Inc.
DIALPAD-AS-AP
BGP report
Ranked 934 of 19,161 networks in United States. World rank 7,958.
Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored
RPKI ROA
Good11 of 11 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 work8 prefixes have an exact route object, 0 are covered by a larger one, 3 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.
- 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.
- Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
Route object with another origin (3)
Upstream redundancy
Good8 upstream, 20 peer, 0 downstream.
With a single upstream, any outage there cuts your whole network off the internet.
Global visibility
Good11 of 11 prefixes are seen by at least half of the full-table feeds worldwide.
Prefixes seen only partly are usually caught by filters (no ROA or route object), too specific, or announced to domestic IXPs only.
IPv6
Good6 IPv6 prefixes announced.
Most mobile users and large services already run on IPv6.
PeeringDB
GoodProfile exists, listed at 3 IX.
Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.
Prefix aggregation
Needs work5 IPv4 prefixes could be summarized into 3.
Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.
- Announce the aggregate when the split is not needed. If it is intended, give every piece its own ROA and route object.
Put the badge on your website
<a href="https://bgp.awancerah.cloud/en/AS134521/rapor"><img src="https://bgp.awancerah.cloud/en/AS134521/rapor.svg" alt="BGP report AS134521"></a>
[](https://bgp.awancerah.cloud/en/AS134521/rapor)