bgpreport

Network · data from 2026-11-12

AS398570 Dedicated IT, LLC

Registry name: DITN - Dedicated IT, LLC, US · PeeringDB

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

Announced routes

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

2605:dcc0::/35 No ROA Nonecovered by 2605:dcc0::/32 635 100% 68
216.250.233.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
216.250.246.0/24 No ROA RIR databaseARIN, RADB 672 100% 66

AS-SET

PeeringDB's irr_as_set for AS398570: AS-DEDICATED-IT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS398570 isn't in the set, or no route object for AS398570 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS398570 in itNot covered
AS-DEDICATED-IT ARIN 113 Yes 0

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

  • ROA: none3
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2605:dcc0::/35No ROA covers it. Add a ROA for AS398570, maxLength 35.635 of 636
Route object: none2605:dcc0::/35No route object for it. A route object for 2605:dcc0::/32 with origin AS398570 covers it (filters allowing more-specifics accept it). Add a route object with origin AS398570 in the RIR database for the space.635 of 636
ROA: none216.250.233.0/24No ROA covers it. Add a ROA for AS398570, maxLength 24.673 of 673
ROA: none216.250.246.0/24No ROA covers it. Add a ROA for AS398570, maxLength 24.672 of 673

Route objects not announced

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

2605:dcc0::/32ARIN, RADBNo 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.