bgpreport

Network · data from 2026-11-12

AS34119 Wildcard Networks

Registry name: WILDCARD-AS Wildcard UK Limited, GB · PeeringDB

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

Announced routes

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

82.138.232.0/22 No ROA RIR databaseRIPE 673 100% 67
82.163.176.0/22 No ROA RIR databaseRIPE 673 100% 67
185.27.132.0/22 No ROA RIR databaseRIPE 671 100% 67
2a04:3bc0::/29 No ROA RIR databaseRIPE 634 100% 67
31.22.0.0/21 Valid RIR databaseRIPE 673 100% 67
31.22.7.0/24 Valid RIR databaseRIPE 673 100% 67
69.30.84.0/24 Valid RIR databaseARIN 673 100% 67
77.95.32.0/21 Valid RIR databaseRIPE 673 100% 67
138.226.208.0/22 Valid RIR databaseRIPE 673 100% 67
149.143.150.0/23 Valid RIR databaseARIN 673 100% 67
149.143.168.0/22 Valid RIR databaseARIN 673 100% 67
158.120.72.0/23 Valid RIR databaseRIPE 673 100% 67
185.2.168.0/22 Valid RIR databaseRIPE 673 100% 67
185.103.228.0/22 Valid RIR databaseRIPE 673 100% 67
185.211.176.0/22 Valid RIR databaseRIPE 673 100% 67
31.22.4.0/24 Valid RIR databaseRIPE 672 100% 67
2a02:5300::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS34119: AS-WILDCARD. 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 (AS34119 isn't in the set, or no route object for AS34119 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 objectsAS34119 in itNot covered
AS-WILDCARD RIPE 4223 Yes 0

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

  • ROA: none4
ChangePrefix or setDetailFull-table peers
ROA: none82.138.232.0/22No ROA covers it. Add a ROA for AS34119, maxLength 22.673 of 673
ROA: none82.163.176.0/22No ROA covers it. Add a ROA for AS34119, maxLength 22.673 of 673
ROA: none185.27.132.0/22No ROA covers it. Add a ROA for AS34119, maxLength 22.671 of 673
ROA: none2a04:3bc0::/29No ROA covers it. Add a ROA for AS34119, maxLength 29.634 of 636

Route objects not announced

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