Routing security
AS50599 Autonomous System for Dataspace P.S.A.
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS50599 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a0a:aac0::/29 | RPKI valid | IRR | 35 |
| 2a0b:5480::/29 | RPKI valid | IRR | 35 |
| 2a02:e7c0::/29 | RPKI valid | IRR | 35 |
| 5.133.115.0/24 | RPKI valid | IRR | 56 |
| 83.150.236.0/24 | RPKI valid | IRR | 53 |
| 89.40.144.0/22 | RPKI valid | IRR | 56 |
| 91.196.14.0/23 | RPKI valid | IRR | 56 |
| 91.204.160.0/23 | RPKI valid | IRR | 56 |
| 91.204.162.0/24 | RPKI valid | IRR | 56 |
| 91.219.184.0/22 | RPKI valid | IRR | 56 |
| 91.224.60.0/23 | RPKI valid | IRR | 56 |
| 91.231.104.0/24 | RPKI valid | IRR | 56 |
| 91.231.105.0/24 | RPKI valid | IRR | 56 |
| 91.231.106.0/24 | RPKI valid | IRR | 56 |
| 91.236.52.0/24 | RPKI valid | IRR | 56 |
| 91.236.54.0/23 | RPKI valid | IRR | 56 |
| 91.244.225.0/24 | RPKI valid | IRR | 56 |
| 128.0.54.0/24 | RPKI valid | IRR | 56 |
| 185.11.128.0/22 | RPKI valid | IRR | 56 |
| 185.72.196.0/22 | RPKI valid | IRR | 56 |
| 185.170.104.0/22 | RPKI valid | IRR | 56 |
| 185.200.44.0/22 | RPKI valid | IRR | 54 |
| 185.216.174.0/23 | RPKI valid | IRR | 56 |
| 185.221.110.0/24 | RPKI valid | IRR | 56 |
| 188.210.220.0/22 | RPKI valid | IRR | 53 |
| 193.105.125.0/24 | RPKI valid | IRR | 56 |
| 194.117.81.0/24 | RPKI valid | IRR | 56 |
| 195.177.216.0/24 | RPKI valid | IRR | 56 |
| 195.177.217.0/24 | RPKI valid | IRR | 56 |
| 213.239.128.0/23 | RPKI valid | IRR | 56 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS50599 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 5.133.115.0/24 | /24 | RIPENCC |
| 83.150.236.0/24 | /24 | RIPENCC |
| 89.40.144.0/22 | /22 | RIPENCC |
| 91.196.14.0/23 | /23 | RIPENCC |
| 91.204.160.0/23 | /23 | RIPENCC |
| 91.204.162.0/24 | /24 | RIPENCC |
| 91.219.184.0/22 | /22 | RIPENCC |
| 91.224.60.0/23 | /23 | RIPENCC |
| 91.231.104.0/24 | /24 | RIPENCC |
| 91.231.105.0/24 | /24 | RIPENCC |
| 91.231.106.0/24 | /24 | RIPENCC |
| 91.236.52.0/24 | /24 | RIPENCC |
| 91.236.54.0/23 | /23 | RIPENCC |
| 91.244.225.0/24 | /24 | RIPENCC |
| 128.0.54.0/24 | /24 | RIPENCC |
| 185.11.128.0/22 | /22 | RIPENCC |
| 185.72.196.0/22 | /22 | RIPENCC |
| 185.170.104.0/22 | /22 | RIPENCC |
| 185.200.44.0/22 | /22 | RIPENCC |
| 185.216.174.0/23 | /23 | RIPENCC |
| 185.221.110.0/24 | /24 | RIPENCC |
| 188.210.220.0/22 | /22 | RIPENCC |
| 193.105.125.0/24 | /24 | RIPENCC |
| 194.117.81.0/24 | /24 | RIPENCC |
| 195.177.216.0/24 | /24 | RIPENCC |
| 195.177.217.0/24 | /24 | RIPENCC |
| 212.7.213.0/24 | /24 | RIPENCC |
| 213.239.128.0/23 | /23 | RIPENCC |
| 2a02:e7c0::/29 | /29 | RIPENCC |
| 2a0a:aac0::/29 | /29 | RIPENCC |
| 2a0b:5480::/29 | /29 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
No ASPA record This network has not published an ASPA object. ASPA lets a network sign the list of its transit providers, so routers can reject paths that route through anyone else (route leaks). Only a few thousand networks publish one so far, so its absence is normal.
IRR
Registered route objects
Route objects naming AS50599 as origin, across RADb, the RIR registries, ALTDB and NTTCOM. Objects that are registered but not announced come first: a stale object lets anyone who can spoof this origin through an IRR-built filter.
| Prefix | Source | Description | Maintainer | Changed | Routing |
|---|---|---|---|---|---|
| 5.133.115.0/24 | RIPE | — | PL-ZFIX-1-MNT | 2026-07-24 | Announced |
| 83.150.236.0/24 | RIPE | — | ITCARE-MNT | 2018-12-24 | Announced |
| 89.40.144.0/22 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 91.196.14.0/23 | RIPE | — | PL-ZFIX-1-MNT | 2025-07-07 | Announced |
| 91.204.160.0/23 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 91.204.162.0/24 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 91.219.184.0/22 | RIPE | IPv4 route for Media4U Sp. z o.o. | M4U-MNT | 2020-08-15 | Announced |
| 91.224.60.0/23 | RIPE | IPv4 route for Ecenter S.A. | DATASPACE-MNT | 2020-08-15 | Announced |
| 91.231.104.0/24 | RIPE | — | PL-ZFIX-1-MNT | 2026-07-24 | Announced |
| 91.231.105.0/24 | RIPE | — | PL-ZFIX-1-MNT | 2026-07-24 | Announced |
| 91.231.106.0/24 | RIPE | — | PL-ZFIX-1-MNT | 2026-07-24 | Announced |
| 91.236.52.0/24 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 91.236.54.0/23 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 91.244.225.0/24 | RIPE | ECENTER S.A. Route | ECSA-MNT | 2013-08-01 | Announced |
| 128.0.54.0/24 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 185.11.128.0/22 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 185.72.196.0/22 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 185.170.104.0/22 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 185.200.44.0/22 | RIPE | IPv4 route for PERSKIMEDIA Szymon Perski | PL-PERSKINET-1-MNT | 2020-08-15 | Announced |
| 185.216.174.0/23 | RIPE | — | PL-ZFIX-1-MNT | 2025-07-07 | Announced |
| 185.221.110.0/24 | RIPE | IPv4 route for MSERWIS Michal Splawski | DATASPACE-MNT | 2020-09-21 | Announced |
| 188.210.220.0/22 | RIPE | IPv4 route for PERSKIMEDIA Szymon Perski | DATASPACE-MNT | 2020-08-15 | Announced |
| 193.105.125.0/24 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 194.117.81.0/24 | RIPE | Bouncer via Dataspace | LIR-PL-USEBOUNCER-1-MNT | 2026-02-17 | Announced |
| 195.177.216.0/24 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 195.177.217.0/24 | RIPE | IPv4 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 213.239.128.0/23 | RIPE | — | LIR-PL-SEOHOST-1-MNT | 2026-07-16 | Announced |
| 2a02:e7c0::/29 | RIPE | IPv6 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
| 2a0a:aac0::/29 | RIPE | IPv6 route for PERSKIMEDIA Szymon Perski | PL-PERSKINET-1-MNT | 2020-08-13 | Announced |
| 2a0b:5480::/29 | RIPE | IPv6 route for Dataspace P.S.A. | DATASPACE-MNT | 2024-06-27 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS50599 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-DATASPACE | RIPE | Lists AS50599 as a direct member |
AS-DATASPACE-PLIX | RIPE | Lists AS50599 as a direct member |
AS-DATASPACE-THINX | RIPE | Lists AS50599 as a direct member |
AS-EXATEL-INT | RIPE | Lists AS50599 as a direct member |
AS-EXATEL-PL | RIPE | Lists AS50599 as a direct member |
AS-HURRICANE | RADB | Lists AS50599 as a direct member |
AS-HURRICANEV6 | RADB | Lists AS50599 as a direct member |
AS-IPARTNERS | RIPE | Lists AS50599 as a direct member |
AS-NETIA | RIPE | Lists AS50599 as a direct member |
AS-NETIA-MSK-IX | RIPE | Lists AS50599 as a direct member |
AS-NETIA-PEERING | RIPE | Lists AS50599 as a direct member |
AS-TKTELEKOM6 | RIPE | Lists AS50599 as a direct member |
AS-TRANSROUTE-SPEC | RIPE | Lists AS50599 as a direct member |
AS24724:AS-FOREIGN | RIPE | Lists AS50599 as a direct member |
AS24724:AS-FOREIGN6 | RIPE | Lists AS50599 as a direct member |
AS29535:AS-MIX2 | RIPE | Lists AS50599 as a direct member |
AS5617:AS-PL | RIPE | Lists AS50599 as a direct member |
AS5617:AS-PL-TRANSIT | RIPE | Lists AS50599 as a direct member |
AS8246:AS-TPNET | RIPE | Lists AS50599 as a direct member |
RPKI from rpki-client, validated 2026-10-15 12:09 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-15. Cross-check on bgp.he.net.