bgpreport

Network · data from 2026-11-12

AS6423 Digital Fortress - AS6423

Registry name: DF-PTL2-3 - Digital Fortress, US · PeeringDB

14IPv4 routes 85.7% RPKI valid · 50.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 7 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS6423, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS6423, 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.
206.103.32.0/19 Invalid: origin None 1 0%low visibility 1
209.162.220.0/22 No ROA None 1 0%low visibility 1
69.30.24.0/24 Valid Nonecovered by 69.30.0.0/18 671 100% 69
69.30.34.0/24 Valid Nonecovered by 69.30.0.0/18 669 99% 69
69.30.104.0/24 Valid Nonecovered by 69.30.96.0/19 1 0%low visibility 1
69.30.106.0/24 Valid Nonecovered by 69.30.96.0/19 1 0%low visibility 1
69.30.107.0/24 Valid Nonecovered by 69.30.96.0/19 1 0%low visibility 1
69.30.0.0/18 Valid RIR databaseARIN, RADB 670 100% 68
69.30.80.0/22 Valid RIR databaseARIN, RADB 670 100% 68
69.30.88.0/24 Valid RIR databaseARIN, RADB 670 100% 68
69.30.90.0/24 Valid RIR databaseARIN, RADB 670 100% 68
69.30.94.0/23 Valid RIR databaseARIN, RADB 670 100% 68
69.30.96.0/19 Valid RIR databaseARIN, RADB 670 100% 68
209.162.220.0/24 Valid RIR databaseARIN, RADB 668 99% 68
2001:19d0:100::/40 Valid RIR databaseARIN, RADB 634 100% 67
2001:19d0:200::/40 Valid RIR databaseARIN, RADB 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS6423: RADB::AS-6423. 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 (AS6423 isn't in the set, or no route object for AS6423 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 objectsAS6423 in itNot covered
RADB::AS-6423 RADB 4123 Yes 2

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

  • ROA: origin1
  • ROA: none1
  • Route object: none7
ChangePrefix or setDetailFull-table peers
ROA: origin206.103.32.0/19ROAs covering it name AS3561, not AS6423. If AS6423 should announce it, add a ROA for AS6423.1 of 673
Route object: none206.103.32.0/19No route object for it. Add a route object with origin AS6423 in the RIR database for the space.1 of 673
ROA: none209.162.220.0/22No ROA covers it. Add a ROA for AS6423, maxLength 22.1 of 673
Route object: none209.162.220.0/22No route object for it. Add a route object with origin AS6423 in the RIR database for the space.1 of 673
Route object: none69.30.24.0/24No route object for it. A route object for 69.30.0.0/18 with origin AS6423 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6423 in the RIR database for the space.671 of 673
Route object: none69.30.34.0/24No route object for it. A route object for 69.30.0.0/18 with origin AS6423 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6423 in the RIR database for the space.669 of 673
Route object: none69.30.104.0/24No route object for it. A route object for 69.30.96.0/19 with origin AS6423 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6423 in the RIR database for the space.1 of 673
Route object: none69.30.106.0/24No route object for it. A route object for 69.30.96.0/19 with origin AS6423 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6423 in the RIR database for the space.1 of 673
Route object: none69.30.107.0/24No route object for it. A route object for 69.30.96.0/19 with origin AS6423 covers it (filters allowing more-specifics accept it). Add a route object with origin AS6423 in the RIR database for the space.1 of 673

Route objects not announced

Every route object with origin AS6423 is announced.

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.