Network · data from 2026-11-12
AS214716 WEYRO WEYRO LTD
Registry name: WEYRO WEYRO LTD, GB · not in PeeringDB
51IPv4 routes
96.1% RPKI valid · 96.1% with a route object
3IPv6 routes
100.0% RPKI valid · 100.0% with a route object
2RPKI invalid
2 origin · 0 maxLength
0No ROA
2 with no route object for this origin
2Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS214716, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS214716, 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.
| 194.87.36.0/24 | Invalid: origin | None | 17 3%low visibility |
| 85.155.226.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 82.152.223.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 85.117.243.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.118.160.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 103.109.234.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 136.148.71.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 145.79.181.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 176.118.189.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 179.69.68.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 185.121.179.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.221.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.240.84.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 201.10.94.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.178.140.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.178.141.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.216.218.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 31.77.62.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.141.131.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.152.139.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.155.98.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.231.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 104.222.180.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 104.249.21.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 130.12.242.0/24 | Valid | RIR databaseARIN | 672 100% |
| 151.242.208.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 155.117.249.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 162.35.231.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 167.104.217.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 172.93.122.0/24 | Valid | RIR databaseARIN | 672 100% |
| 185.177.230.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.236.8.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.255.114.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.87.159.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.184.247.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.130.137.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 216.86.70.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 37.221.108.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 80.76.44.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 81.31.210.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 83.136.49.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 85.31.53.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 136.148.74.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 136.148.79.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 143.246.182.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 167.104.223.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.160.71.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 193.202.113.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.86.159.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.31.211.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 82.29.79.0/24 | Valid | RIR databaseRADB, RIPE | 662 98% |
| 2a0f:b240:e::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a0f:b240:13::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a0f:b240:18::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS214716 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 4 are in fix.csv.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 194.87.36.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS214716 should announce it, add a ROA for AS214716. |
| Route object: none | 194.87.36.0/24 | No route object for it. Add a route object with origin AS214716 in the RIR database for the space. |
| ROA: origin | 85.155.226.0/24 | ROAs covering it name AS61138, AS213535, not AS214716. If AS214716 should announce it, add a ROA for AS214716. |
| Route object: none | 85.155.226.0/24 | Route objects for it name AS213535. Add a route object with origin AS214716 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS214716 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.