bgpreport

Network · data from 2026-11-12

AS18259 HIGE - NTT DOCOMO BUSINESS, Inc

Registry name: HIGE - NTT DOCOMO BUSINESS, Inc, JP · not in PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 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
27Route objects not announced registered with origin AS18259, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS18259, 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.178.96.0/20 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
202.178.96.0/21 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
202.178.104.0/22 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
202.178.104.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
202.178.106.0/23 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
202.178.108.0/22 Valid RIR databaseAPNIC, NTTCOM 673 100% 67
2001:218:2200::/40 Valid RIR databaseAPNIC, NTTCOM 635 100% 67
2401:4640::/32 Valid RIR databaseAPNIC, NTTCOM 635 100% 67

AS-SET

AS18259 isn't in PeeringDB, where networks name their 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 27 are in fix.csv.

  • Route object: not announced27

Route objects not announced

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

163.138.241.0/24APNIC, NTTCOMValid
163.138.242.0/24APNIC, NTTCOMValid
202.178.96.0/22APNIC, NTTCOMValid
202.178.96.0/23APNIC, NTTCOMValid
202.178.96.0/24APNIC, NTTCOMValid
202.178.97.0/24APNIC, NTTCOMValid
202.178.98.0/23APNIC, NTTCOMValid
202.178.98.0/24APNIC, NTTCOMValid
202.178.99.0/24APNIC, NTTCOMValid
202.178.100.0/22APNIC, NTTCOMValid
202.178.100.0/23APNIC, NTTCOMValid
202.178.100.0/24APNIC, NTTCOMValid
202.178.101.0/24APNIC, NTTCOMValid
202.178.102.0/23APNIC, NTTCOMValid
202.178.102.0/24APNIC, NTTCOMValid
202.178.103.0/24APNIC, NTTCOMValid
202.178.104.0/21APNIC, NTTCOMValid
202.178.104.0/23APNIC, NTTCOMValid
202.178.105.0/24APNIC, NTTCOMValid
202.178.106.0/24APNIC, NTTCOMValid
202.178.107.0/24APNIC, NTTCOMValid
202.178.108.0/23APNIC, NTTCOMValid
202.178.108.0/24APNIC, NTTCOMValid
202.178.109.0/24APNIC, NTTCOMValid
202.178.110.0/23APNIC, NTTCOMValid
202.178.110.0/24APNIC, NTTCOMValid
202.178.111.0/24APNIC, NTTCOMValid

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.