Routing security
AS62033 HOSTERS
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS62033 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 2a06:c980::/29 | RPKI valid | IRR | 30 |
| 2a10:5d80::/29 | RPKI valid | IRR | 30 |
| 2a10:5d80:1::/48 | RPKI valid | IRR covering | 30 |
| 45.132.34.0/24 | RPKI valid | IRR | 51 |
| 87.121.134.0/24 | RPKI valid | IRR | 51 |
| 87.121.135.0/24 | RPKI valid | IRR | 50 |
| 91.92.248.0/24 | RPKI valid | IRR | 54 |
| 91.92.249.0/24 | RPKI valid | IRR | 50 |
| 185.127.128.0/24 | RPKI valid | IRR | 51 |
| 185.127.129.0/24 | RPKI valid | IRR | 54 |
| 185.127.130.0/24 | RPKI valid | IRR | 51 |
| 185.127.131.0/24 | RPKI valid | IRR | 51 |
| 188.130.183.0/24 | RPKI valid | IRR | 51 |
| 216.176.232.0/22 | RPKI valid | IRR | 51 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS62033 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 45.132.34.0/24 | /24 | RIPENCC |
| 87.121.134.0/24 | /24 | RIPENCC |
| 87.121.135.0/24 | /24 | RIPENCC |
| 91.92.248.0/24 | /24 | RIPENCC |
| 91.92.249.0/24 | /24 | RIPENCC |
| 185.127.128.0/24 | /24 | RIPENCC |
| 185.127.129.0/24 | /24 | RIPENCC |
| 185.127.130.0/24 | /24 | RIPENCC |
| 185.127.131.0/24 | /24 | RIPENCC |
| 188.130.183.0/24 | /24 | RIPENCC |
| 216.176.232.0/22 | /22 | RIPENCC |
| 216.176.232.0/24 | /24 | RIPENCC |
| 216.176.233.0/24 | /24 | RIPENCC |
| 216.176.234.0/24 | /24 | RIPENCC |
| 216.176.235.0/24 | /24 | RIPENCC |
| 2a06:c980::/29 | /29 | RIPENCC |
| 2a10:5d80::/29 | /29 | RIPENCC |
| 2a10:5d80:1::/48 | /48 | RIPENCC |
ROA-based and RPKI-valid-only prefix lists for routers are on asn.ipinfo.app.
RPKI · ASPA
Declared transit providers
This network has signed an ASPA record naming its transit providers. Each is compared against the upstreams observed in routing paths.
| AS | Network | ASPA | Routing paths |
|---|---|---|---|
| AS13287 | FALBOX S.L. trading as NIXVAL | Declared | Observed |
| AS16276 | OVH SAS | Declared | Observed |
| AS34927 | iFog GmbH | Declared | not observed |
| AS174 | Cogent Communications, LLC | not declared | Observed |
| AS61953 | CLOUDEUS SL | not declared | Observed |
An observed upstream that is not declared is not necessarily a leak: our upstream inference cannot tell a transit provider from a peer seen in the same position. A declared provider that is never observed is usually a backup path.
IRR
Registered route objects
Route objects naming AS62033 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 |
|---|---|---|---|---|---|
| 87.121.134.0/23 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-04-13 | Not announced |
| 91.92.248.0/23 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-04-13 | Not announced |
| 216.176.232.0/24 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-03-27 | Not announced |
| 216.176.233.0/24 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-03-27 | Not announced |
| 216.176.234.0/24 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-03-27 | Not announced |
| 216.176.235.0/24 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-03-27 | Not announced |
| 45.132.34.0/24 | RIPE | — | MNT-ES-HOSTERS-1 | 2020-11-09 | Announced |
| 87.121.134.0/24 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-03-08 | Announced |
| 87.121.135.0/24 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-02-11 | Announced |
| 91.92.248.0/24 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-01-14 | Announced |
| 91.92.249.0/24 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-01-14 | Announced |
| 185.127.128.0/24 | RIPE | — | AS13287-MNT | 2026-07-15 | Announced |
| 185.127.129.0/24 | RIPE | — | MNT-ES-HOSTERS-1 | 2020-11-12 | Announced |
| 185.127.130.0/24 | RIPE | — | AS13287-MNT | 2026-07-15 | Announced |
| 185.127.131.0/24 | RIPE | — | AS13287-MNT | 2026-07-09 | Announced |
| 188.130.183.0/24 | RIPE | — | AS13287-MNT | 2026-07-15 | Announced |
| 216.176.232.0/22 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-03-23 | Announced |
| 2a06:c980::/29 | RIPE | — | AS13287-MNT | 2026-07-22 | Announced |
| 2a10:5d80::/29 | RIPE | — | MNT-ES-HOSTERS-1 | 2026-07-22 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS62033 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-IFOG | RIPE | Lists AS62033 as a direct member |
AS-NIXVAL-TRANSIT | RIPE | Lists AS62033 as a direct member |
AS-NTX | RIPE | Lists AS62033 as a direct member |
AS-NTX32 | RIPE | Lists AS62033 as a direct member |
AS-OVH | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-AMSTERDAM | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-ASHBURN | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-AUCKLAND | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-FRANKFURT | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-FREMONT | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-KANSASCITY | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-NEWARK | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-SINGAPORE | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-STOCKHOLM | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-SYDNEY | RIPE | Lists AS62033 as a direct member |
AS52025:AS-DOWNSTREAMS-TORONTO | RIPE | Lists AS62033 as a direct member |
AS61953:AS-TRANSIT | RIPE | Lists AS62033 as a direct member |
RPKI from rpki-client, validated 2026-10-14 18:17 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-14. Cross-check on bgp.he.net.