bgpreport

Network · data from 2026-11-12

AS30277 DFW-DATACENTER - DFW Datacenter

Registry name: DFW-DATACENTER - DFW Datacenter, US · not in PeeringDB

20IPv4 routes 65.0% RPKI valid · 40.0% with a route object
4IPv6 routes 0.0% RPKI valid · 25.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
10No ROA 15 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS30277, seen from no peer

Announced routes

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

103.68.200.0/24 Invalid: origin Other origin only 1 0%low visibility 1
158.106.188.0/22 No ROA Other origin only 673 100% 67
170.249.252.0/22 No ROA Other origin only 673 100% 67
2606:db00:d::/48 No ROA Nonecovered by 2606:db00::/32 635 100% 68
2606:db00:e::/48 No ROA Nonecovered by 2606:db00::/32 635 100% 68
2606:db00:f::/48 No ROA Nonecovered by 2606:db00::/32 635 100% 68
158.106.184.0/22 No ROA Other IRR onlyRADB 673 100% 67
162.222.212.0/24 No ROA Other IRR onlyRADB 673 100% 67
170.249.248.0/22 No ROA Other IRR onlyRADB 673 100% 67
196.53.113.0/24 No ROA Other IRR onlyRADB 673 100% 67
2606:db00::/32 No ROA RIR databaseARIN 634 100% 68
67.222.138.0/24 Valid Nonecovered by 67.222.128.0/19 673 100% 67
67.222.140.0/24 Valid Nonecovered by 67.222.128.0/19 673 100% 67
72.9.152.0/21 Valid Nonecovered by 72.9.144.0/20 672 100% 67
209.236.112.0/21 Valid Nonecovered by 209.236.112.0/20 672 100% 67
209.236.120.0/21 Valid Nonecovered by 209.236.112.0/20 672 100% 67
209.236.126.0/24 Valid Nonecovered by 209.236.112.0/20 672 100% 67
67.222.128.0/20 Valid Nonecovered by 67.222.128.0/19 670 100% 67
67.222.144.0/20 Valid Nonecovered by 67.222.128.0/19 670 100% 67
72.9.144.0/21 Valid Nonecovered by 72.9.144.0/20 669 99% 67
67.222.128.0/19 Valid RIR databaseARIN, RADB 673 100% 67
72.9.144.0/20 Valid RIR databaseARIN 672 100% 67
199.26.84.0/22 Valid RIR databaseARIN 672 100% 67
209.236.112.0/20 Valid RIR databaseARIN 672 100% 67

AS-SET

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

  • ROA: origin1
  • ROA: none10
  • Route object: none15
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: origin103.68.200.0/24ROAs covering it name AS40747, not AS30277. If AS30277 should announce it, add a ROA for AS30277.1 of 673
Route object: none103.68.200.0/24Route objects for it name AS40747. Add a route object with origin AS30277 in the RIR database for the space.1 of 673
ROA: none158.106.188.0/22No ROA covers it. Add a ROA for AS30277, maxLength 22.673 of 673
Route object: none158.106.188.0/22Route objects for it name AS63410, AS393398. Add a route object with origin AS30277 in the RIR database for the space.673 of 673
ROA: none170.249.252.0/22No ROA covers it. Add a ROA for AS30277, maxLength 22.673 of 673
Route object: none170.249.252.0/22Route objects for it name AS63410, AS393398. Add a route object with origin AS30277 in the RIR database for the space.673 of 673
ROA: none2606:db00:d::/48No ROA covers it. Add a ROA for AS30277, maxLength 48.635 of 636
Route object: none2606:db00:d::/48No route object for it. A route object for 2606:db00::/32 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.635 of 636
ROA: none2606:db00:e::/48No ROA covers it. Add a ROA for AS30277, maxLength 48.635 of 636
Route object: none2606:db00:e::/48No route object for it. A route object for 2606:db00::/32 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.635 of 636
ROA: none2606:db00:f::/48No ROA covers it. Add a ROA for AS30277, maxLength 48.635 of 636
Route object: none2606:db00:f::/48No route object for it. A route object for 2606:db00::/32 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.635 of 636
ROA: none158.106.184.0/22No ROA covers it. Add a ROA for AS30277, maxLength 22.673 of 673
Route object: RIR158.106.184.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none162.222.212.0/24No ROA covers it. Add a ROA for AS30277, maxLength 24.673 of 673
Route object: RIR162.222.212.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none170.249.248.0/22No ROA covers it. Add a ROA for AS30277, maxLength 22.673 of 673
Route object: RIR170.249.248.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none196.53.113.0/24No ROA covers it. Add a ROA for AS30277, maxLength 24.673 of 673
Route object: RIR196.53.113.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2606:db00::/32No ROA covers it. Add a ROA for AS30277, maxLength 32.634 of 636
Route object: none67.222.138.0/24No route object for it. A route object for 67.222.128.0/19 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.673 of 673
Route object: none67.222.140.0/24No route object for it. A route object for 67.222.128.0/19 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.673 of 673
Route object: none72.9.152.0/21No route object for it. A route object for 72.9.144.0/20 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.672 of 673
Route object: none209.236.112.0/21No route object for it. A route object for 209.236.112.0/20 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.672 of 673
Route object: none209.236.120.0/21No route object for it. A route object for 209.236.112.0/20 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.672 of 673
Route object: none209.236.126.0/24No route object for it. A route object for 209.236.112.0/20 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.672 of 673
Route object: none67.222.128.0/20No route object for it. A route object for 67.222.128.0/19 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.670 of 673
Route object: none67.222.144.0/20No route object for it. A route object for 67.222.128.0/19 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.670 of 673
Route object: none72.9.144.0/21No route object for it. A route object for 72.9.144.0/20 with origin AS30277 covers it (filters allowing more-specifics accept it). Add a route object with origin AS30277 in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS30277 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.