AwanCerahBGP
Home/Japan/AS4713
Autonomous System

NTT DOCOMO BUSINESS,Inc.

AS4713JapanAPNIC · since 1995NSPPeering: Selective

OCN

B81/100Good

BGP report

Ranked 303 of 754 networks in Japan, 85 of 131 ISPs and transit networks. World rank 23,822.

  • RPKI ROA12/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility10/10
  • IPv610/10
  • PeeringDB9/10
  • Prefix aggregation5/5

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

Score history

RPKI ROA

Needs work
12/30

76 of 189 prefixes have a matching ROA (valid). 113 without a ROA.

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

How to fix
  1. Create a ROA for every prefix in the portal of the RIR or NIR that holds it: MyAPNIC, the IDNIC member portal, the RIPE NCC LIR Portal, ARIN Online, MyAFRINIC or MiLACNIC.
  2. The ROA origin must be the AS that actually announces the prefix. Set maxLength to the announced length; a loose maxLength leaves room for sub-prefix hijacks.
Prefixes without a ROA (113)
27.133.240.0/2261.4.152.0/2361.4.154.0/2361.4.156.0/2261.4.160.0/2461.4.161.0/2461.4.162.0/2461.4.163.0/2461.4.164.0/2261.4.168.0/2261.4.172.0/2261.114.112.0/2161.114.120.0/21103.163.250.0/23119.161.104.0/21133.153.0.0/16133.153.22.0/24138.212.224.0/24138.212.225.0/24138.212.227.0/24138.212.228.0/24138.212.229.0/24138.212.230.0/24138.212.238.0/24138.212.239.0/24138.212.241.0/24138.212.245.0/24138.212.249.0/24138.212.252.0/24150.5.64.0/18150.35.0.0/16150.35.235.0/24150.61.4.0/24150.61.8.0/24150.61.13.0/24150.61.17.0/24150.61.31.0/24150.61.33.0/24150.61.35.0/24150.61.41.0/24150.61.46.0/24150.61.49.0/24150.61.53.0/24150.61.64.0/18150.61.70.0/24150.61.128.0/17153.124.192.0/21157.64.0.0/16157.120.124.0/24157.120.125.0/24157.120.126.0/24157.120.127.0/24159.211.22.0/24159.211.224.0/24159.211.237.0/24159.211.248.0/24164.43.141.0/24164.162.4.0/24164.162.5.0/24164.162.6.0/24164.162.7.0/24164.162.16.0/24165.108.0.0/16165.241.0.0/21165.241.8.0/22165.241.12.0/22165.241.16.0/20165.241.32.0/19165.241.64.0/18165.241.128.0/17182.161.76.0/22198.232.16.0/24202.18.209.0/24202.18.210.0/24202.19.152.0/24202.34.80.0/24202.34.81.0/24202.34.82.0/24202.34.83.0/24202.34.90.0/24202.34.92.0/24202.34.93.0/24202.34.94.0/24202.34.100.0/24202.34.102.0/24202.34.103.0/24202.34.104.0/24202.34.106.0/24202.34.107.0/24202.34.108.0/23202.34.110.0/24202.34.111.0/24202.157.100.0/24202.157.101.0/24202.157.102.0/24202.157.103.0/24202.157.112.0/22202.157.116.0/22202.157.120.0/22202.157.124.0/24202.157.125.0/24202.213.16.0/22202.216.26.0/24202.246.122.0/23202.246.176.0/22202.255.27.0/24202.255.28.0/23210.134.16.0/20210.171.200.0/21211.1.32.0/192400:7800::/322407:a800:3e11:111a::/642407:a800:3e12::/48

IRR route objects

Good
20/20

189 prefixes have an exact route object, 0 are covered by a larger one, 0 have none.

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

Upstream redundancy

Good
15/15

5 upstream, 6 peer, 112 downstream.

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

Upstream (5)

Global visibility

Needs work
10/10

187 of 189 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.

How to fix
  1. Check the ROA and route object of those prefixes, and keep them no longer than /24 for IPv4 or /48 for IPv6.
Prefixes with low visibility (2)

IPv6

Good
10/10

6 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Needs work
9/10

Profile exists, listed at 3 IX. Missing: 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

183 IPv4 prefixes could be summarized into 143.

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

Dropping invalid routes (ROV)

Note

Seen passing on 3 RPKI-invalid routes of other networks in sampled paths. This suggests the AS does not drop all invalid routes, for example those from its customers.

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

How to fix
  1. Run an RPKI validator (for example Routinator or rpki-client) and reject invalid routes on your BGP sessions. MikroTik RouterOS 7 supports this through /routing rpki and the rpki-verify filter.
Example invalid routes (3)

Put the badge on your website

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