bgpreport

Network · data from 2026-11-12

AS207208 Mevspace - Internet Service

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS207208, 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.
5.181.191.0/24 Valid RIR databaseRIPE 671 100% 68
31.77.75.0/24 Valid RIR databaseRIPE 671 100% 68
80.47.28.0/22 Valid RIR databaseRIPE 671 100% 68
82.108.210.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
149.50.120.0/24 Valid RIR databaseARIN, RADB 671 100% 68
149.50.123.0/24 Valid RIR databaseARIN, RADB 671 100% 68
153.76.221.0/24 Valid RIR databaseRIPE 671 100% 68
178.95.185.0/24 Valid RIR databaseRADB, RIPE 671 100% 68
217.60.92.0/24 Valid RIR databaseRIPE 671 100% 68
217.60.93.0/24 Valid RIR databaseRIPE 671 100% 68
2001:67c:2498::/48 Valid RIR databaseRIPE 635 100% 69
2a09:d581::/32 Valid RIR databaseRIPE 635 100% 69
2a10:fa81:1b00::/48 Valid RIR databaseRIPE 635 100% 69
2a11:b100:e100::/48 Valid RIR databaseRIPE 634 100% 69
2a0f:2f80::/29 Valid RIR databaseRIPE 632 99% 69
80.47.28.0/23 Valid RIR databaseRIPE 292 43% 59
80.47.30.0/23 Valid RIR databaseRIPE 292 43% 59

AS-SET

PeeringDB's irr_as_set for AS207208: AS207208: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 (AS207208 isn't in the set, or no route object for AS207208 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 objectsAS207208 in itNot covered
AS207208:AS-CLIENTS RIPE2 member sets in no database: AS212112:AS-NOVITSKIY, AS213702:AS-CUSTOMERS 74118,395 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.

  • AS-SET: missing member2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberAS207208:AS-CLIENTSAS207208:AS-CLIENTS (RIPE) lists AS212112:AS-NOVITSKIY; no IRR database read has it.
AS-SET: missing memberAS207208:AS-CLIENTSAS207208:AS-CLIENTS (RIPE) lists AS213702:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

48.103.222.0/24RIPEValid
2a0f:b240:1400::/40RIPEValid

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.