bgpreport

Network · data from 2026-11-12

AS21778 NET-DIDATA-NY - Dimension Data North America, Inc.

Registry name: NET-DIDATA-NY - Dimension Data North America, Inc., US · not in PeeringDB

11IPv4 routes 90.9% 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
1No ROA 0 with no route object for this origin
6Low visibility seen by under 10% of full-table peers
7Route objects not announced registered with origin AS21778, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS21778, 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.
204.56.94.0/24 No ROA Other IRR onlyALTDB 673 100% 67
128.241.34.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
129.250.40.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
129.250.161.0/24 Valid Other IRR onlyNTTCOM 673 100% 67
204.2.200.0/23 Valid Other IRR onlyNTTCOM 673 100% 67
2001:418:9808::/48 Valid Other IRR onlyNTTCOM 636 100% 67
129.250.161.128/27 Valid Other IRR onlyNTTCOM 28 4%low visibility 22
165.254.21.160/27 Valid Other IRR onlyNTTCOM 28 4%low visibility 22
165.254.119.64/27 Valid Other IRR onlyNTTCOM 28 4%low visibility 22
204.0.1.192/27 Valid Other IRR onlyNTTCOM 28 4%low visibility 22
204.2.193.16/29 Valid Other IRR onlyNTTCOM 28 4%low visibility 22
207.55.138.24/29 Valid Other IRR onlyNTTCOM 28 4%low visibility 22

AS-SET

AS21778 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 20 are in fix.csv.

  • ROA: none1
  • Route object: RIR12
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none204.56.94.0/24No ROA covers it. Add a ROA for AS21778, maxLength 24.673 of 673
Route object: RIR204.56.94.0/24Route object only in ALTDB. Add it in the RIR database for the space.673 of 673
Route object: RIR128.241.34.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR129.250.40.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR129.250.161.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR204.2.200.0/23Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR2001:418:9808::/48Route object only in NTTCOM. Add it in the RIR database for the space.636 of 636
Route object: RIR129.250.161.128/27Route object only in NTTCOM. Add it in the RIR database for the space.28 of 673
Route object: RIR165.254.21.160/27Route object only in NTTCOM. Add it in the RIR database for the space.28 of 673
Route object: RIR165.254.119.64/27Route object only in NTTCOM. Add it in the RIR database for the space.28 of 673
Route object: RIR204.0.1.192/27Route object only in NTTCOM. Add it in the RIR database for the space.28 of 673
Route object: RIR204.2.193.16/29Route object only in NTTCOM. Add it in the RIR database for the space.28 of 673
Route object: RIR207.55.138.24/29Route object only in NTTCOM. Add it in the RIR database for the space.28 of 673

Route objects not announced

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

165.254.27.16/29NTTCOMValid
165.254.27.24/29NTTCOMValid
204.2.42.160/27NTTCOMValid
204.56.87.0/24ALTDBNo ROA
204.56.95.0/24ALTDBNo ROA
2001:418:1401:68::/64NTTCOMValid
2001:418:1451::/48NTTCOMValid

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.