AS201814
MEVSPACE sp. z o.o.
AS201814 is MEVSPACE sp. z o.o. (mevspace.com). It announces 25,856 IPv4 addresses in 48 prefixes, and 4 IPv6 prefixes.
Poland· RIPE· allocated 2014-07-03· hosting
25,856
IPv4 addresses announced
48
IPv4 prefixes
4
IPv6 prefixes
96.15%
of its routes RPKI-valid
25,856
of its IPv4 geolocated
5
countries
Where its space is
The IPv4 it announces that IP Geolocation places, by country. A /24 counts for the AS announcing most of it.
- Poland23,808 · 92.08%
- United Kingdom768 · 2.97%
- Germany512 · 1.98%
- The Netherlands512 · 1.98%
- Bulgaria256 · 0.99%
Registry record
Its ASN Whois record, as the registry publishes it.
- handle
- Mevspace
- name
- MEVSPACE sp. z o.o.
- org
- ORG-MSZO78-RIPE
- org name
- MEVSPACE sp. z o.o.
- org address
- Augustyna Locciego 33, 02-928, Warszawa, POLAND
- org country
- PL
- country
- PL
- source
- ripe
- status
- ASSIGNED
- created
- 2014-07-03
- updated
- 2026-09-01
- remarks
- Communities used with AS201814 / Communities for specific links are aut_num:x / x=1,2,3 prepend, x=9 do not advertise / for AS174 Cogent Communications 174:x / for AS1299 Arelion 1299:x / for AS6939 Hurricane Electric 6939:x / for AS29535 TPIX 29535:x / for AS50263 1-IX 50263:x / for AS50952 GNM-IX 50952:x / for AS59613 Giganet 59613:x / 65535:666 - Blackhole community / We accept /32 ipv4 prefixes and /128 ipv6 prefixes, / - if they have the blackhole community set, / - if they are in your as-set object.
- maintainer
- RIPE-NCC-END-MNT|SKYTECH-MNT
- abuse name
- Abuse-C Role
- abuse email
- abuse@mevspace.com
- abuse kind
- role
What the databases see
Addresses each address-keyed database holds in the IPv4 it announces, as a share of that space, with its largest providers. Counts overlap.
- VPN IP311browsec, rodnetvpn, xeovo1.20%
- geonode, anyip, onesproxy1.79%
- floppydata0.01%
- dataimpulse, floppydata0.07%
- 0.02%
- None here
- Hosting IP17,40867.33%
- None here
- None here
- None here
- SSH IP4,34316.80%
- SMTP IP4171.61%
- DNS Resolver IP1,9337.48%
IPv4 prefixes
Every IPv4 prefix BGP Route saw it announce. A prefix another AS also announces says so.
| PREFIX | COUNTRY | RPKI | PEERS | FIRST SEEN |
|---|---|---|---|---|
| 5.181.188.0/22 | Poland | valid | 18 | 2026-10-02 |
| 45.129.196.0/24 | Poland | valid | 18 | 2026-10-02 |
| 45.141.233.0/24 | United Kingdom | valid | 18 | 2026-10-02 |
| 77.73.129.0/24 | Poland | valid | 18 | 2026-10-02 |
| 77.90.188.0/24 | Poland | valid | 18 | 2026-10-02 |
| 80.47.0.0/19 | Poland | valid | 18 | 2026-10-02 |
| 80.47.0.0/20 | Poland | valid | 5 | 2026-10-02 |
| 80.47.16.0/20 | Poland | valid | 5 | 2026-10-02 |
| 82.22.10.0/24 | Poland | valid | 18 | 2026-10-02 |
| 91.223.3.0/24 | Poland | valid | 18 | 2026-10-02 |
| 91.226.198.0/23 | Poland | valid | 18 | 2026-10-02 |
| 91.226.198.0/24 | Poland | valid | 5 | 2026-10-02 |
| 91.226.199.0/24 | Poland | valid | 5 | 2026-10-02 |
| 91.234.255.0/24 | Poland | valid | 18 | 2026-10-02 |
| 94.26.68.0/24 | Bulgaria | valid | 18 | 2026-10-02 |
| 94.26.88.0/24 | United Kingdom | valid | 18 | 2026-10-02 |
| 95.214.52.0/22 | Poland | valid | 18 | 2026-10-02 |
| 95.214.52.0/23 | Poland | valid | 5 | 2026-10-02 |
| 95.214.54.0/23 | Poland | valid | 5 | 2026-10-02 |
| 104.245.245.0/24 | Poland | valid | 18 | 2026-10-02 |
| 109.205.211.0/24 | The Netherlands | valid | 18 | 2026-10-02 |
| 146.19.24.0/24 | Poland | valid | 18 | 2026-10-02 |
| 149.50.96.0/19 | Poland | not found | 18 | 2026-10-02 |
| 149.50.96.0/20 | Poland | valid | 18 | 2026-10-02 |
| 149.50.96.0/21 | Poland | valid | 5 | 2026-10-02 |
| 149.50.104.0/21 | Poland | valid | 5 | 2026-10-02 |
| 149.50.112.0/20 | Poland | valid | 18 | 2026-10-02 |
| 149.50.112.0/21 | Poland | valid | 5 | 2026-10-02 |
| 149.50.120.0/21 | Poland | valid | 5 | 2026-10-02 |
| 149.86.224.0/22 | Poland | not found | 18 | 2026-10-02 |
| 168.222.10.0/24 | Poland | valid | 18 | 2026-10-02 |
| 178.211.139.0/24 | Poland | valid | 18 | 2026-10-02 |
| 185.16.36.0/22 | Poland | valid | 18 | 2026-10-02 |
| 185.56.44.0/24 | Poland | valid | 18 | 2026-10-02 |
| 185.225.191.0/24 | Poland | valid | 18 | 2026-10-02 |
| 185.248.24.0/24 | Poland | valid | 18 | 2026-10-02 |
| 185.252.132.0/24 | The Netherlands | valid | 18 | 2026-10-02 |
| 191.44.80.0/24 | United Kingdom | valid | 18 | 2026-10-02 |
| 191.44.81.0/24 | Poland | valid | 18 | 2026-10-02 |
| 193.34.212.0/22 | Poland | valid | 18 | 2026-10-02 |
| 193.34.212.0/23 | Poland | valid | 5 | 2026-10-02 |
| 193.34.214.0/23 | Poland | valid | 5 | 2026-10-02 |
| 194.180.48.0/24 | Germany | valid | 18 | 2026-10-02 |
| 194.180.49.0/24 | Germany | valid | 18 | 2026-10-02 |
| 195.3.220.0/22 | Poland | valid | 18 | 2026-10-02 |
| 195.3.220.0/23 | Poland | valid | 18 | 2026-10-02 |
| 195.3.222.0/23 | Poland | valid | 18 | 2026-10-02 |
| 212.23.222.0/24 | Poland | valid | 18 | 2026-10-02 |
IPv6 prefixes
Every IPv6 prefix BGP Route saw it announce.
00 · Evaluate
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.
01 · License
Then license what you use.
Standard, for detection and decisions inside your own product and operations.
Redistribution, when the data ships onward inside what you sell — priced by scope, not by seat.
Annual terms, a named contact, and flexible payment terms — monthly, quarterly or yearly.