bgpreport

Network · data from 2026-11-12

AS201814 Mevspace

Registry name: Mevspace MEVSPACE sp. z o.o., PL · PeeringDB

55IPv4 routes 87.3% RPKI valid · 90.9% with a route object
4IPv6 routes 100.0% RPKI valid · 100.0% with a route object
5RPKI invalid 5 origin · 0 maxLength
2No ROA 5 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
24Route objects not announced registered with origin AS201814, seen from no peer

Announced routes

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

2.26.255.0/32 Invalid: origin None 0 0%low visibility 1
31.41.33.137/32 Invalid: origin None 0 0%low visibility 1
31.41.33.138/32 Invalid: origin None 0 0%low visibility 1
31.41.33.211/32 Invalid: origin None 0 0%low visibility 1
144.31.102.115/32 Invalid: origin None 0 0%low visibility 1
149.50.96.0/19 No ROA Other IRR onlyRADB 671 100% 68
149.86.224.0/22 No ROA Other IRR onlyRADB, RIPE-NONAUTH 671 100% 68
5.181.188.0/22 Valid RIR databaseRIPE 671 100% 68
45.129.196.0/24 Valid RIR databaseRIPE 671 100% 68
77.73.129.0/24 Valid RIR databaseRIPE 671 100% 68
80.47.0.0/19 Valid RIR databaseRIPE 671 100% 68
82.22.10.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
91.223.3.0/24 Valid RIR databaseRIPE 671 100% 68
91.226.198.0/23 Valid RIR databaseRIPE 671 100% 68
91.234.255.0/24 Valid RIR databaseRIPE 671 100% 68
104.245.245.0/24 Valid RIR databaseARIN, RADB 671 100% 68
168.222.10.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
178.211.139.0/24 Valid RIR databaseRIPE 671 100% 68
185.16.36.0/22 Valid RIR databaseRIPE 671 100% 68
185.56.44.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
185.225.191.0/24 Valid RIR databaseRIPE 671 100% 68
185.252.132.0/24 Valid RIR databaseRIPE 671 100% 68
191.44.80.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
191.44.81.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
193.34.212.0/22 Valid RIR databaseRIPE 671 100% 68
195.3.220.0/22 Valid RIR databaseRIPE 671 100% 68
212.23.222.0/24 Valid RIR databaseRIPE 671 100% 68
77.90.188.0/24 Valid RIR databaseRIPE 670 100% 68
45.141.233.0/24 Valid RIR databaseRIPE 668 99% 68
94.26.68.0/24 Valid RIR databaseRIPE 668 99% 68
95.214.52.0/22 Valid RIR databaseRIPE 668 99% 68
109.205.211.0/24 Valid RIR databaseRIPE 668 99% 68
146.19.24.0/24 Valid RIR databaseRIPE 668 99% 68
149.50.96.0/20 Valid RIR databaseARIN, RADB 668 99% 68
149.50.112.0/20 Valid RIR databaseARIN, RADB 668 99% 68
185.248.24.0/24 Valid RIR databaseRIPE 668 99% 68
194.180.48.0/24 Valid RIR databaseRIPE 668 99% 68
194.180.49.0/24 Valid RIR databaseRIPE 668 99% 68
94.26.88.0/24 Valid RIR databaseRIPE 661 98% 68
2a03:cfc0::/32 Valid RIR databaseRIPE 634 100% 69
2a12:a800:2::/48 Valid RIR databaseRIPE 634 100% 69
2a03:cfc0:8000::/33 Valid RIR databaseRIPE 633 100% 69
2a09:d580::/29 Valid RIR databaseRIPE 633 100% 69
195.3.222.0/23 Valid RIR databaseRIPE 293 44% 59
80.47.16.0/20 Valid RIR databaseRIPE 292 43% 59
91.226.198.0/24 Valid RIR databaseRIPE 292 43% 59
91.226.199.0/24 Valid RIR databaseRIPE 292 43% 59
193.34.212.0/23 Valid RIR databaseRIPE 292 43% 59
193.34.214.0/23 Valid RIR databaseRIPE 292 43% 59
149.50.112.0/21 Valid RIR databaseARIN, RADB 290 43% 59
195.3.220.0/23 Valid RIR databaseRIPE 290 43% 59
80.47.0.0/20 Valid RIR databaseRIPE 289 43% 59
95.214.52.0/23 Valid RIR databaseRIPE 289 43% 59
95.214.54.0/23 Valid RIR databaseRIPE 289 43% 59
149.50.96.0/21 Valid RIR databaseARIN, RADB 287 43% 59
149.50.104.0/21 Valid RIR databaseARIN, RADB 287 43% 59
149.50.120.0/21 Valid RIR databaseARIN, RADB 287 43% 59
185.16.36.0/23 Valid RIR databaseRIPE 6 1%low visibility 2
185.16.38.0/23 Valid RIR databaseRIPE 6 1%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS201814: AS201814:AS-CLIENTS. 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 (AS201814 isn't in the set, or no route object for AS201814 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 objectsAS201814 in itNot covered
AS201814:AS-CLIENTS RIPE2 member sets in no database: AS212112:AS-NOVITSKIY, AS213702:AS-CUSTOMERS 106129,375 Yes 5

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

  • ROA: origin5
  • ROA: none2
  • Route object: none5
  • Route object: RIR2
  • AS-SET: missing member2
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
ROA: origin2.26.255.0/32ROAs covering it name AS198550, AS207567, not AS201814. If AS201814 should announce it, add a ROA for AS201814.0 of 673
Route object: none2.26.255.0/32No route object for it. Add a route object with origin AS201814 in the RIR database for the space.0 of 673
ROA: origin31.41.33.137/32ROAs covering it name AS48014, not AS201814. If AS201814 should announce it, add a ROA for AS201814.0 of 673
Route object: none31.41.33.137/32No route object for it. Add a route object with origin AS201814 in the RIR database for the space.0 of 673
ROA: origin31.41.33.138/32ROAs covering it name AS48014, not AS201814. If AS201814 should announce it, add a ROA for AS201814.0 of 673
Route object: none31.41.33.138/32No route object for it. Add a route object with origin AS201814 in the RIR database for the space.0 of 673
ROA: origin31.41.33.211/32ROAs covering it name AS48014, not AS201814. If AS201814 should announce it, add a ROA for AS201814.0 of 673
Route object: none31.41.33.211/32No route object for it. Add a route object with origin AS201814 in the RIR database for the space.0 of 673
ROA: origin144.31.102.115/32ROAs covering it name AS207513, not AS201814. If AS201814 should announce it, add a ROA for AS201814.0 of 673
Route object: none144.31.102.115/32No route object for it. Add a route object with origin AS201814 in the RIR database for the space.0 of 673
ROA: none149.50.96.0/19No ROA covers it. Add a ROA for AS201814, maxLength 19.671 of 673
Route object: RIR149.50.96.0/19Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none149.86.224.0/22No ROA covers it. Add a ROA for AS201814, maxLength 22.671 of 673
Route object: RIR149.86.224.0/22Route object only in RADB, RIPE-NONAUTH. Add it in the RIR database for the space.671 of 673
AS-SET: missing memberAS201814:AS-CLIENTSAS201814:AS-CLIENTS (RIPE) lists AS212112:AS-NOVITSKIY; no IRR database read has it.
AS-SET: missing memberAS201814:AS-CLIENTSAS201814:AS-CLIENTS (RIPE) lists AS213702:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

5.181.188.0/23RIPEInvalid: maxLength
5.181.190.0/23RIPEInvalid: maxLength
31.59.137.0/24RADB, RIPEValid
45.80.158.0/24RIPEValid
45.138.16.0/24RIPEValid
45.192.12.0/24RADBValid
45.198.0.0/24RADBValid
82.108.210.0/24RADB, RIPEValid
91.199.222.0/24RIPENo ROA
91.206.169.0/24RIPEValid
149.86.224.0/23ARIN, RADBValid
149.86.226.0/23ARIN, RADBValid
178.95.185.0/24RADB, RIPEValid
185.241.208.0/24RIPEValid
193.8.187.0/24RIPEValid
193.34.215.0/24RIPEValid
193.35.110.0/24RIPEValid
193.41.129.0/24RIPEValid
195.3.222.0/24RIPEValid
195.128.154.0/24RIPEValid
2001:470:327::/48ARINValid
2001:67c:2498::/48RIPEInvalid: origin
2a03:cfc0::/33RIPEValid
2a03:cfc0:8000::/34RIPEValid

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.