bgpreport

Network · data from 2026-11-12

AS40061 UL-ASN-LAX1 - UnitedLayer, LLC

Registry name: UL-ASN-LAX1 - UnitedLayer, LLC, US · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 0.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 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS40061, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS40061, 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.
207.7.141.0/24 No ROA None 673 100% 67
207.7.150.0/24 No ROA Other origin only 673 100% 67
2607:f3a0:2000::/35 No ROA None 635 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none3
ChangePrefix or setDetailFull-table peers
ROA: none207.7.141.0/24No ROA covers it. Add a ROA for AS40061, maxLength 24.673 of 673
Route object: none207.7.141.0/24No route object for it. Add a route object with origin AS40061 in the RIR database for the space.673 of 673
ROA: none207.7.150.0/24No ROA covers it. Add a ROA for AS40061, maxLength 24.673 of 673
Route object: none207.7.150.0/24Route objects for it name AS22279. Add a route object with origin AS40061 in the RIR database for the space.673 of 673
ROA: none2607:f3a0:2000::/35No ROA covers it. Add a ROA for AS40061, maxLength 35.635 of 636
Route object: none2607:f3a0:2000::/35No route object for it. Add a route object with origin AS40061 in the RIR database for the space.635 of 636

Route objects not announced

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