bgpreport

Network · data from 2026-11-12

AS53834 DINCL - dinCloud Inc.

Registry name: DINCL - dinCloud Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53834, 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.

2607:b00::/33 No ROA Nonecovered by 2607:b00::/32 635 100% 67
162.245.8.0/23 No ROA RIR databaseARIN 673 100% 67
162.245.10.0/23 No ROA RIR databaseARIN 673 100% 67
162.245.12.0/22 No ROA RIR databaseARIN 673 100% 67
198.246.188.0/22 No ROA RIR databaseARIN, NTTCOM 673 100% 67
199.187.128.0/23 No ROA RIR databaseARIN 673 100% 67
199.187.130.0/24 No ROA RIR databaseARIN 673 100% 67
199.187.131.0/24 No ROA RIR databaseARIN 673 100% 67
162.245.8.0/22 No ROA RIR databaseARIN 672 100% 67
199.187.128.0/22 No ROA RIR databaseARIN 672 100% 67

AS-SET

AS53834 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.

  • ROA: none10
  • Route object: none1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none2607:b00::/33No ROA covers it. Add a ROA for AS53834, maxLength 33.635 of 636
Route object: none2607:b00::/33No route object for it. A route object for 2607:b00::/32 with origin AS53834 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53834 in the RIR database for the space.635 of 636
ROA: none162.245.8.0/23No ROA covers it. Add a ROA for AS53834, maxLength 23.673 of 673
ROA: none162.245.10.0/23No ROA covers it. Add a ROA for AS53834, maxLength 23.673 of 673
ROA: none162.245.12.0/22No ROA covers it. Add a ROA for AS53834, maxLength 22.673 of 673
ROA: none198.246.188.0/22No ROA covers it. Add a ROA for AS53834, maxLength 22.673 of 673
ROA: none199.187.128.0/23No ROA covers it. Add a ROA for AS53834, maxLength 23.673 of 673
ROA: none199.187.130.0/24No ROA covers it. Add a ROA for AS53834, maxLength 24.673 of 673
ROA: none199.187.131.0/24No ROA covers it. Add a ROA for AS53834, maxLength 24.673 of 673
ROA: none162.245.8.0/22No ROA covers it. Add a ROA for AS53834, maxLength 22.672 of 673
ROA: none199.187.128.0/22No ROA covers it. Add a ROA for AS53834, maxLength 22.672 of 673

Route objects not announced

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

162.245.8.0/24ARINNo ROA
162.245.9.0/24ARINNo ROA
162.245.10.0/24ARINNo ROA
162.245.11.0/24ARINNo ROA
162.245.12.0/24ARINNo ROA
162.245.13.0/24ARINNo ROA
162.245.14.0/24ARINNo ROA
162.245.15.0/24ARINNo ROA
198.246.188.0/24ARINNo ROA
198.246.189.0/24ARINNo ROA
198.246.190.0/24ARINNo ROA
198.246.191.0/24ARINNo ROA
199.187.128.0/24ARINNo ROA
199.187.129.0/24ARINNo ROA
2607:b00::/32RADBNo ROA
2607:b00:8000::/33RADBNo ROA

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.