bgpreport

Network · data from 2026-11-12

AS50599 DATASPACE-PL

Registry name: DATASPACE DATASPACE P.S.A., PL · PeeringDB

27IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 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
0Route objects not announced registered with origin AS50599, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS50599, 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.
83.150.236.0/24 Valid RIR databaseRIPE 673 100% 66
185.200.44.0/22 Valid RIR databaseRIPE 673 100% 66
5.133.115.0/24 Valid RIR databaseRIPE 671 100% 68
89.40.144.0/22 Valid RIR databaseRIPE 671 100% 68
91.196.14.0/23 Valid RIR databaseRIPE 671 100% 68
91.204.160.0/23 Valid RIR databaseRIPE 671 100% 68
91.204.162.0/24 Valid RIR databaseRIPE 671 100% 68
91.219.184.0/22 Valid RIR databaseRIPE 671 100% 68
91.224.60.0/23 Valid RIR databaseRIPE 671 100% 68
91.231.104.0/24 Valid RIR databaseRIPE 671 100% 68
91.231.105.0/24 Valid RIR databaseRIPE 671 100% 68
91.231.106.0/24 Valid RIR databaseRIPE 671 100% 68
91.236.52.0/24 Valid RIR databaseRIPE 671 100% 68
91.236.54.0/23 Valid RIR databaseRIPE 671 100% 68
91.244.225.0/24 Valid RIR databaseRIPE 671 100% 68
185.11.128.0/22 Valid RIR databaseRIPE 671 100% 68
185.72.196.0/22 Valid RIR databaseRIPE 671 100% 68
185.170.104.0/22 Valid RIR databaseRIPE 671 100% 68
185.216.174.0/23 Valid RIR databaseRIPE 671 100% 68
185.221.110.0/24 Valid RIR databaseRIPE 671 100% 68
193.105.125.0/24 Valid RIR databaseRIPE 671 100% 68
194.117.81.0/24 Valid RIR databaseRIPE 671 100% 68
195.177.216.0/24 Valid RIR databaseRIPE 671 100% 68
195.177.217.0/24 Valid RIR databaseRIPE 671 100% 68
213.239.128.0/23 Valid RIR databaseRIPE 671 100% 68
128.0.54.0/24 Valid RIR databaseRIPE 670 100% 68
188.210.220.0/22 Valid RIR databaseRIPE 670 100% 66
2a02:e7c0::/29 Valid RIR databaseRIPE 634 100% 69
2a0a:aac0::/29 Valid RIR databaseRIPE 634 100% 69
2a0b:5480::/29 Valid RIR databaseRIPE 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS50599: AS-DATASPACE. 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 (AS50599 isn't in the set, or no route object for AS50599 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 objectsAS50599 in itNot covered
AS-DATASPACE RIPE 2130 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS50599 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.