bgpreport

Network · data from 2026-11-12

AS7587 ACCESSNETWORKS - TRANSMEDIA-ID

Registry name: ACCESSNETWORKS - TRANSMEDIA-ID, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS7587, 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.
2001:d68::/48 Valid Other IRR onlyNTTCOM, RADB 634 100% 68
202.180.0.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 67
202.180.1.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 67

AS-SET

AS7587 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 34 are in fix.csv.

  • Route object: RIR1
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
Route object: RIR2001:d68::/48Route object only in NTTCOM, RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

202.180.0.0/19APNIC, NTTCOMNo ROA
202.180.0.0/20NTTCOMNo ROA
202.180.0.0/21NTTCOMNo ROA
202.180.0.0/22NTTCOMNo ROA
202.180.0.0/23NTTCOMNo ROA
202.180.2.0/23NTTCOMNo ROA
202.180.2.0/24APNIC, NTTCOMNo ROA
202.180.3.0/24APNIC, NTTCOMNo ROA
202.180.4.0/22NTTCOMNo ROA
202.180.4.0/23NTTCOMNo ROA
202.180.4.0/24APNIC, NTTCOMNo ROA
202.180.5.0/24APNIC, NTTCOMNo ROA
202.180.6.0/23NTTCOMNo ROA
202.180.6.0/24APNIC, NTTCOMNo ROA
202.180.7.0/24APNICInvalid: origin
202.180.8.0/21NTTCOMNo ROA
202.180.8.0/22NTTCOMNo ROA
202.180.8.0/23NTTCOMNo ROA
202.180.8.0/24APNICInvalid: origin
202.180.9.0/24APNICInvalid: origin
202.180.10.0/23NTTCOMNo ROA
202.180.10.0/24APNICInvalid: origin
202.180.11.0/24APNICInvalid: origin
202.180.12.0/24APNICInvalid: origin
202.180.13.0/24APNICInvalid: origin
202.180.14.0/24APNICInvalid: origin
202.180.15.0/24APNICInvalid: origin
202.180.16.0/24APNICInvalid: origin
202.180.18.0/24APNICInvalid: origin
202.180.21.0/24APNICInvalid: origin
202.180.22.0/24APNICInvalid: origin
202.180.23.0/24APNICInvalid: origin
2001:d68:1::/48RADBValid

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.