bgpreport

Network · data from 2026-11-12

AS37900 NTT DOCOMO BUSINESS, Inc. AS37900

Registry name: MATSURI - NTT DOCOMO BUSINESS, Inc., JP · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS37900, 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.
202.2.89.0/24 Valid Other IRR onlyJPIRR 673 100% 67
202.2.91.0/24 Valid Other IRR onlyJPIRR 670 100% 67
2402:c800:fff1::/48 Valid Other IRR onlyJPIRR 635 100% 67
2402:c800:fff6::/48 Valid Other IRR onlyJPIRR 635 100% 67
2402:c800:fff3::/48 Valid Other IRR onlyJPIRR 634 100% 70
202.4.244.0/24 Valid RIR databaseAPNIC, JPIRR 673 100% 67
202.4.245.0/24 Valid RIR databaseAPNIC, JPIRR 673 100% 67

AS-SET

AS37900's PeeringDB record names no 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 14 are in fix.csv.

  • Route object: RIR5
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: RIR202.2.89.0/24Route object only in JPIRR. Add it in the RIR database for the space.673 of 673
Route object: RIR202.2.91.0/24Route object only in JPIRR. Add it in the RIR database for the space.670 of 673
Route object: RIR2402:c800:fff1::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:c800:fff6::/48Route object only in JPIRR. Add it in the RIR database for the space.635 of 636
Route object: RIR2402:c800:fff3::/48Route object only in JPIRR. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

202.2.88.0/24JPIRRValid
202.2.90.0/24JPIRR, RADBValid
202.4.244.0/22APNICValid
202.4.244.0/23APNICValid
202.4.246.0/23APNICValid
202.4.246.0/24APNICValid
202.4.247.0/24APNICValid
2402:c800:fff4::/48JPIRRValid
2402:c800:fff5::/48JPIRRValid

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.