bgpreport

Network · data from 2026-11-12

AS273894 273894

Registry name: AS273894 - U2RED S.A.S, CO · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS273894, 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.
23.27.191.0/24 Invalid: origin Other origin only 0 0%low visibility 1
38.172.205.0/24 No ROA None 0 0%low visibility 1
38.224.21.0/24 No ROA None 0 0%low visibility 1
2803:430:cafe::/48 Valid Nonecovered by 2803:430::/32 636 100% 67
64.204.90.0/24 Valid RIR databaseARIN, RADB 672 100% 67
107.149.165.0/24 Valid RIR databaseARIN, RADB 672 100% 67
2803:430::/32 Valid RIR databaseLACNIC 636 100% 67

AS-SET

AS273894's PeeringDB record names no 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 7 are in fix.csv.

  • ROA: origin1
  • ROA: none2
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: origin23.27.191.0/24ROAs covering it name AS212238, not AS273894. If AS273894 should announce it, add a ROA for AS273894.0 of 673
Route object: none23.27.191.0/24Route objects for it name AS212238. Add a route object with origin AS273894 in the RIR database for the space.0 of 673
ROA: none38.172.205.0/24No ROA covers it. Add a ROA for AS273894, maxLength 24.0 of 673
Route object: none38.172.205.0/24No route object for it. Add a route object with origin AS273894 in the RIR database for the space.0 of 673
ROA: none38.224.21.0/24No ROA covers it. Add a ROA for AS273894, maxLength 24.0 of 673
Route object: none38.224.21.0/24No route object for it. Add a route object with origin AS273894 in the RIR database for the space.0 of 673
Route object: none2803:430:cafe::/48No route object for it. A route object for 2803:430::/32 with origin AS273894 covers it (filters allowing more-specifics accept it). Add a route object with origin AS273894 in the RIR database for the space.636 of 636

Route objects not announced

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