bgpreport

Network · data from 2026-11-12

AS401182 APPLIEDDIGITAL

Registry name: APPLIEDDIGITAL - Applied Digital Corporation, US · PeeringDB

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

Announced routes

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

131.143.54.0/24 No ROA RIR databaseARIN, RADB 670 100% 68
69.2.199.0/24 No ROA RIR databaseARIN, RADB 119 18% 31
172.252.7.0/24 Valid RIR databaseARIN, RADB 673 100% 67
172.252.69.0/24 Valid RIR databaseARIN, RADB 673 100% 67
172.252.178.0/24 Valid RIR databaseARIN, RADB 673 100% 67
172.252.187.0/24 Valid RIR databaseARIN, RADB 673 100% 67
208.184.129.0/24 Valid RIR databaseARIN 672 100% 67
208.184.135.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS401182: ARIN::AS401182:AS-APLD. 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 (AS401182 isn't in the set, or no route object for AS401182 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 objectsAS401182 in itNot covered
ARIN::AS401182:AS-APLD ARIN 3323 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: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none131.143.54.0/24No ROA covers it. Add a ROA for AS401182, maxLength 24.670 of 673
ROA: none69.2.199.0/24No ROA covers it. Add a ROA for AS401182, maxLength 24.119 of 673

Route objects not announced

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

64.78.177.0/24ARINNo ROA
172.252.50.0/24ARIN, RADBValid
172.252.126.0/24ARIN, RADBValid

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.