bgpreport

Network · data from 2026-11-12

AS40545 Empire Access

Registry name: EMPIRE-40545 - Empire Access, US · PeeringDB

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

Announced routes

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

38.145.160.0/19 No ROA None 2 0%low visibility 2
38.162.128.0/18 No ROA None 2 0%low visibility 2
38.240.240.0/20 No ROA None 2 0%low visibility 2
38.246.84.0/23 No ROA Other IRR onlyRADB 671 100% 68
38.254.18.0/23 No ROA Other IRR onlyRADB 671 100% 68
52.124.59.0/24 No ROA Other IRR onlyRADB 671 100% 68
74.118.28.0/22 No ROA Other IRR onlyRADB 671 100% 68
162.210.112.0/22 No ROA Other IRR onlyALTDB, RADB 671 100% 68
66.115.64.0/20 Valid RIR databaseARIN, RADB 671 100% 68
72.18.48.0/20 Valid RIR databaseARIN, RADB 671 100% 68
104.255.84.0/22 Valid RIR databaseARIN, RADB 671 100% 68
152.55.64.0/18 Valid RIR databaseARIN, RADB 671 100% 68
161.13.64.0/18 Valid RIR databaseARIN, RADB 671 100% 68
199.190.196.0/23 Valid RIR databaseARIN, RADB 671 100% 68
2606:380::/32 Valid RIR databaseARIN, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS40545: AS40545:AS-EMPIRE-ALL. 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 (AS40545 isn't in the set, or no route object for AS40545 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 objectsAS40545 in itNot covered
AS40545:AS-EMPIRE-ALL RADB 6269 Yes 3
ARIN (also) 6269 Yes 3

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

  • ROA: none8
  • Route object: none3
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none38.145.160.0/19No ROA covers it. Add a ROA for AS40545, maxLength 19.2 of 673
Route object: none38.145.160.0/19No route object for it. Add a route object with origin AS40545 in the RIR database for the space.2 of 673
ROA: none38.162.128.0/18No ROA covers it. Add a ROA for AS40545, maxLength 18.2 of 673
Route object: none38.162.128.0/18No route object for it. Add a route object with origin AS40545 in the RIR database for the space.2 of 673
ROA: none38.240.240.0/20No ROA covers it. Add a ROA for AS40545, maxLength 20.2 of 673
Route object: none38.240.240.0/20No route object for it. Add a route object with origin AS40545 in the RIR database for the space.2 of 673
ROA: none38.246.84.0/23No ROA covers it. Add a ROA for AS40545, maxLength 23.671 of 673
Route object: RIR38.246.84.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none38.254.18.0/23No ROA covers it. Add a ROA for AS40545, maxLength 23.671 of 673
Route object: RIR38.254.18.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none52.124.59.0/24No ROA covers it. Add a ROA for AS40545, maxLength 24.671 of 673
Route object: RIR52.124.59.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none74.118.28.0/22No ROA covers it. Add a ROA for AS40545, maxLength 22.671 of 673
Route object: RIR74.118.28.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none162.210.112.0/22No ROA covers it. Add a ROA for AS40545, maxLength 22.671 of 673
Route object: RIR162.210.112.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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