bgpreport

Network · data from 2026-11-12

AS213887 WAICORE

Registry name: WAICORE-LTD WAIcore Ltd, GB · PeeringDB

63IPv4 routes 98.4% RPKI valid · 87.3% with a route object
10IPv6 routes 90.0% RPKI valid · 50.0% with a route object
1RPKI invalid 1 origin · 0 maxLength
1No ROA 13 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS213887, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213887, 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.
212.192.246.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2a0d:d940:1c00::/40 No ROA RIR databaseRIPE 635 100% 69
85.137.254.0/24 Valid Nonecovered by 85.137.254.0/23 673 100% 67
85.137.255.0/24 Valid Nonecovered by 85.137.254.0/23 673 100% 67
109.122.196.0/23 Valid Nonecovered by 109.122.196.0/22 673 100% 67
109.122.196.0/24 Valid Nonecovered by 109.122.196.0/22 673 100% 67
109.122.197.0/24 Valid Nonecovered by 109.122.196.0/22 673 100% 67
109.122.198.0/24 Valid Nonecovered by 109.122.196.0/22 673 100% 67
109.122.199.0/24 Valid Nonecovered by 109.122.196.0/22 671 100% 66
2a0b:4141::/36 Valid Nonecovered by 2a0b:4141::/32 636 100% 67
2a0b:4141:e000::/36 Valid Nonecovered by 2a0b:4141::/32 636 100% 67
2a0b:4141:1000::/36 Valid Nonecovered by 2a0b:4141::/32 635 100% 67
2a0b:4141:9000::/36 Valid Nonecovered by 2a0b:4141::/32 635 100% 67
2a0b:4141:9835::/48 Valid Nonecovered by 2a0b:4141::/32 104 16% 32
87.120.92.0/24 Valid RIR databaseRIPE 673 100% 67
87.120.205.0/24 Valid RIR databaseRIPE 673 100% 67
87.120.216.0/24 Valid RIR databaseRIPE 673 100% 67
94.141.123.0/24 Valid RIR databaseRIPE 673 100% 67
95.85.230.0/24 Valid RIR databaseRIPE 673 100% 67
95.85.231.0/24 Valid RIR databaseRIPE 673 100% 67
95.85.232.0/24 Valid RIR databaseRIPE 673 100% 67
95.85.233.0/24 Valid RIR databaseRIPE 673 100% 67
95.85.234.0/24 Valid RIR databaseRIPE 673 100% 67
95.85.235.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.6.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.8.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.9.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.28.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.32.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.33.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.36.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.37.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.38.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.39.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.44.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.45.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.46.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.47.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.48.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.56.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.57.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.82.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.83.0/24 Valid RIR databaseRIPE 673 100% 67
178.17.48.0/24 Valid RIR databaseRIPE 673 100% 67
178.17.49.0/24 Valid RIR databaseRIPE 673 100% 67
178.17.50.0/24 Valid RIR databaseRIPE 673 100% 67
178.17.51.0/24 Valid RIR databaseRIPE 673 100% 67
178.17.52.0/24 Valid RIR databaseRIPE 673 100% 67
178.17.60.0/24 Valid RIR databaseRIPE 673 100% 67
178.17.61.0/24 Valid RIR databaseRIPE 673 100% 67
193.233.134.0/24 Valid RIR databaseRIPE 673 100% 67
193.233.254.0/24 Valid RIR databaseRIPE 673 100% 67
194.87.29.0/24 Valid RIR databaseRIPE 673 100% 67
194.87.77.0/24 Valid RIR databaseRIPE 673 100% 67
213.165.55.0/24 Valid RIR databaseRIPE 673 100% 67
213.165.56.0/24 Valid RIR databaseRIPE 673 100% 67
213.165.57.0/24 Valid RIR databaseRIPE 673 100% 67
213.165.58.0/24 Valid RIR databaseRIPE 673 100% 67
213.176.76.0/24 Valid RIR databaseRIPE 673 100% 67
213.176.77.0/24 Valid RIR databaseRIPE 673 100% 67
213.176.78.0/24 Valid RIR databaseRIPE 673 100% 67
138.124.7.0/24 Valid RIR databaseRIPE 671 100% 67
138.124.17.0/24 Valid RIR databaseRIPE 671 100% 67
213.165.59.0/24 Valid RIR databaseRIPE 671 100% 67
213.165.54.0/24 Valid RIR databaseRIPE 670 100% 68
138.124.40.0/24 Valid RIR databaseRIPE 669 99% 68
138.124.41.0/24 Valid RIR databaseRIPE 669 99% 68
138.124.42.0/24 Valid RIR databaseRIPE 669 99% 68
138.124.43.0/24 Valid RIR databaseRIPE 669 99% 68
2a0d:d940:1e00::/40 Valid RIR databaseRIPE 635 100% 67
2a14:7583:a800::/38 Valid RIR databaseRIPE 634 100% 67
2a14:7583:5700::/40 Valid RIR databaseRIPE 633 100% 67
2a14:7583:ac00::/38 Valid RIR databaseRIPE 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS213887: RIPE::AS-WAICORE. 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 (AS213887 isn't in the set, or no route object for AS213887 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 objectsAS213887 in itNot covered
RIPE::AS-WAICORE RIPE 91186 Yes 1

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

  • ROA: origin1
  • ROA: none1
  • Route object: none13
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: origin212.192.246.0/24ROAs covering it name AS207353, not AS213887. If AS213887 should announce it, add a ROA for AS213887.2 of 673
Route object: none212.192.246.0/24Route objects for it name AS207353. Add a route object with origin AS213887 in the RIR database for the space.2 of 673
ROA: none2a0d:d940:1c00::/40No ROA covers it. Add a ROA for AS213887, maxLength 40.635 of 636
Route object: none85.137.254.0/24No route object for it. A route object for 85.137.254.0/23 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.673 of 673
Route object: none85.137.255.0/24No route object for it. A route object for 85.137.254.0/23 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.673 of 673
Route object: none109.122.196.0/23No route object for it. A route object for 109.122.196.0/22 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.673 of 673
Route object: none109.122.196.0/24No route object for it. A route object for 109.122.196.0/22 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.673 of 673
Route object: none109.122.197.0/24No route object for it. A route object for 109.122.196.0/22 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.673 of 673
Route object: none109.122.198.0/24No route object for it. A route object for 109.122.196.0/22 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.673 of 673
Route object: none109.122.199.0/24No route object for it. A route object for 109.122.196.0/22 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.671 of 673
Route object: none2a0b:4141::/36No route object for it. A route object for 2a0b:4141::/32 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.636 of 636
Route object: none2a0b:4141:e000::/36No route object for it. A route object for 2a0b:4141::/32 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.636 of 636
Route object: none2a0b:4141:1000::/36No route object for it. A route object for 2a0b:4141::/32 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.635 of 636
Route object: none2a0b:4141:9000::/36No route object for it. A route object for 2a0b:4141::/32 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.635 of 636
Route object: none2a0b:4141:9835::/48No route object for it. A route object for 2a0b:4141::/32 with origin AS213887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS213887 in the RIR database for the space.104 of 636

Route objects not announced

Route objects with origin AS213887 whose prefix no peer sees AS213887 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.145.56.0/24RIPEValid
45.149.147.0/24RIPEValid
85.137.254.0/23RIPEValid
109.122.196.0/22RIPEValid
178.17.49.0/25RIPEInvalid: maxLength
185.126.67.0/24RIPEValid
195.66.24.0/24RIPEValid
2a0b:4141::/32RIPEValid
2a0f:cdc6:2000::/44RIPENo ROA
2a0f:cdc6:5000::/44RIPENo ROA
2a0f:cdc6:5010::/44RIPENo ROA
2a0f:cdc6:5020::/44RIPENo ROA
2a14:a087:3::/48RIPEValid
2a14:a087:4::/48RIPEValid

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.