Routing security
AS39537 HNS www.hns.net
Unclassified RIPE
Announcements
What this network originates
Every prefix observed with AS39537 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 91.207.50.0/23 | No ROA | IRR | 51 |
| 2a03:25e0::/36 | RPKI valid | No IRR | 30 |
| 2a09:fd40::/48 | RPKI valid | IRR other origin | 29 |
| 37.35.88.0/21 | RPKI valid | IRR other origin | 51 |
| 94.199.184.0/21 | RPKI valid | IRR other origin | 51 |
| 185.202.115.0/24 | RPKI valid | IRR other origin | 51 |
| 2a01:500::/32 | RPKI valid | IRR | 31 |
| 31.210.128.0/21 | RPKI valid | IRR | 51 |
| 31.210.132.0/24 | RPKI valid | IRR | 51 |
| 45.145.180.0/22 | RPKI valid | IRR | 51 |
| 87.237.64.0/21 | RPKI valid | IRR | 51 |
| 93.95.8.0/21 | RPKI valid | IRR | 51 |
| 93.95.8.0/22 | RPKI valid | IRR | 51 |
| 93.95.12.0/22 | RPKI valid | IRR | 51 |
| 94.190.240.0/21 | RPKI valid | IRR | 51 |
| 94.190.242.0/23 | RPKI valid | IRR covering | 51 |
| 109.69.80.0/21 | RPKI valid | IRR | 51 |
| 151.236.208.0/21 | RPKI valid | IRR | 51 |
| 185.49.236.0/22 | RPKI valid | IRR | 51 |
| 185.68.0.0/22 | RPKI valid | IRR | 51 |
| 185.71.24.0/22 | RPKI valid | IRR | 51 |
| 185.71.26.0/24 | RPKI valid | IRR | 51 |
| 185.105.64.0/23 | RPKI valid | IRR | 51 |
| 185.105.66.0/23 | RPKI valid | IRR | 51 |
| 185.122.216.0/22 | RPKI valid | IRR | 51 |
| 195.94.112.0/20 | RPKI valid | IRR | 51 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS39537 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 31.210.128.0/21 | /24 | RIPENCC |
| 37.35.88.0/21 | /24 | RIPENCC |
| 45.145.180.0/22 | /24 | RIPENCC |
| 87.237.64.0/21 | /24 | RIPENCC |
| 93.95.8.0/21 | /24 | RIPENCC |
| 94.190.240.0/21 | /24 | RIPENCC |
| 94.199.184.0/21 | /24 | RIPENCC |
| 109.69.80.0/21 | /24 | RIPENCC |
| 151.236.208.0/21 | /24 | RIPENCC |
| 185.11.240.0/22 | /24 | RIPENCC |
| 185.31.252.0/22 | /24 | RIPENCC |
| 185.33.184.0/22 | /24 | RIPENCC |
| 185.49.236.0/22 | /24 | RIPENCC |
| 185.68.0.0/22 | /24 | RIPENCC |
| 185.71.24.0/22 | /24 | RIPENCC |
| 185.105.64.0/23 | /24 | RIPENCC |
| 185.105.66.0/23 | /24 | RIPENCC |
| 185.122.216.0/22 | /24 | RIPENCC |
| 185.202.115.0/24 | /24 | RIPENCC |
| 195.94.112.0/20 | /24 | RIPENCC |
| 2a00:e620::/32 | /36 | RIPENCC |
| 2a01:500::/29 | /32 | RIPENCC |
| 2a01:b280::/29 | /36 | RIPENCC |
| 2a03:25e0::/32 | /36 | RIPENCC |
| 2a04:5ac0::/29 | /36 | RIPENCC |
| 2a09:fd40::/48 | /48 | RIPENCC |
| 2a0a:fd80::/29 | /36 | 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 AS39537 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 |
|---|---|---|---|---|---|
| 31.210.128.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 31.210.129.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 31.210.130.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 31.210.131.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 31.210.133.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 31.210.134.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 31.210.135.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 37.35.88.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 37.35.88.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 37.35.88.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 37.35.89.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 37.35.90.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 37.35.90.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 37.35.91.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 37.35.92.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 37.35.92.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 37.35.92.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 37.35.93.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 37.35.94.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 37.35.94.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 37.35.95.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 45.145.180.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 45.145.180.0/24 | RIPE | — | SYSGROUP-MNT | 2022-04-05 | Not announced |
| 45.145.181.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 45.145.182.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 45.145.182.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 45.145.183.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 87.237.64.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 87.237.65.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 87.237.66.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 87.237.67.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 87.237.68.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 87.237.69.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 87.237.70.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 87.237.71.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 93.95.8.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 93.95.8.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 93.95.9.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 93.95.10.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 93.95.10.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 93.95.11.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 93.95.12.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 93.95.12.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 93.95.13.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 93.95.14.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 93.95.14.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 93.95.15.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 94.190.240.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-03-31 | Not announced |
| 94.190.241.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-03-31 | Not announced |
| 94.190.242.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-03-31 | Not announced |
| 94.190.243.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-03-31 | Not announced |
| 94.190.244.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-03-31 | Not announced |
| 94.190.245.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-03-31 | Not announced |
| 94.190.246.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-03-31 | Not announced |
| 94.190.247.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-03-31 | Not announced |
| 94.199.184.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 94.199.184.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 94.199.184.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 94.199.185.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 94.199.186.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 94.199.186.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 94.199.187.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 94.199.188.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 94.199.188.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 94.199.188.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 94.199.189.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 94.199.190.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 94.199.190.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 94.199.191.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 109.69.80.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 109.69.81.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 109.69.82.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 109.69.83.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 109.69.84.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 109.69.85.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 109.69.86.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 109.69.87.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Not announced |
| 151.236.208.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 151.236.208.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 151.236.210.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 151.236.210.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 151.236.211.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 151.236.212.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 151.236.212.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 151.236.212.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 151.236.213.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 151.236.214.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 151.236.214.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 151.236.215.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.11.240.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.11.240.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.11.241.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.11.242.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.11.242.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.11.243.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.31.252.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.31.252.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.31.252.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.31.253.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.31.254.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.31.254.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.31.255.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.33.184.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.33.184.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.33.184.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-MNT | 2020-08-04 | Not announced |
| 185.33.185.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-MNT | 2020-08-04 | Not announced |
| 185.33.186.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.33.186.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-MNT | 2020-08-04 | Not announced |
| 185.33.187.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-MNT | 2020-08-04 | Not announced |
| 185.49.236.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2014-05-27 | Not announced |
| 185.49.237.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2014-05-27 | Not announced |
| 185.49.238.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2014-05-27 | Not announced |
| 185.49.239.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2014-05-27 | Not announced |
| 185.68.0.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.68.0.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.68.1.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.68.2.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.68.2.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.68.3.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.71.24.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.71.24.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.71.25.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.71.26.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.71.27.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.105.64.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.105.64.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.105.65.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.105.66.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.105.67.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.122.216.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.122.216.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.122.217.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.122.218.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 185.122.218.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 185.122.219.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 195.94.112.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.113.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.114.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.115.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.116.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.117.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.118.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.119.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.120.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.121.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.122.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.123.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.124.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.125.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.126.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.94.127.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2017-10-09 | Not announced |
| 195.189.124.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 195.189.124.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 195.189.124.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 195.189.125.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 195.189.126.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Not announced |
| 195.189.126.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 195.189.127.0/24 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-01-05 | Not announced |
| 31.210.128.0/21 | RIPE | Hub Network Services Ltd | MNT-HNS | 2014-08-22 | Announced |
| 31.210.132.0/24 | RIPE | Hub Network Services Ltd | MNT-HNS | 2011-06-22 | Announced |
| 45.145.180.0/22 | RIPE | — | SYSGROUP-MNT | 2022-04-05 | Announced |
| 87.237.64.0/21 | RIPE | Hub Network Services Ltd | MNT-HNS | 2014-08-22 | Announced |
| 91.207.50.0/23 | RIPE | See AS39537 for contact details | MNT-HNS | 2017-06-12 | Announced |
| 93.95.8.0/21 | RIPE | — | SYSGROUP-MNT | 2022-05-04 | Announced |
| 93.95.8.0/22 | RIPE | — | SYSGROUP-MNT | 2022-05-09 | Announced |
| 93.95.12.0/22 | RIPE | — | SYSGROUP-MNT | 2022-05-09 | Announced |
| 94.190.240.0/21 | RIPE | Hub Network Services Ltd | MNT-HNS | 2020-04-06 | Announced |
| 109.69.80.0/21 | RIPE | Hub Network Services Ltd | MNT-HNS | 2014-08-22 | Announced |
| 151.236.208.0/21 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2025-02-17 | Announced |
| 185.49.236.0/22 | RIPE | Hub Network Services Ltd | MNT-HNS | 2014-05-23 | Announced |
| 185.68.0.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Announced |
| 185.71.24.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Announced |
| 185.71.26.0/24 | RIPE | — | SYSGROUP-MNT | 2022-01-08 | Announced |
| 185.105.64.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Announced |
| 185.105.66.0/23 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Announced |
| 185.122.216.0/22 | RIPE | Route not advertised, DDoS mitigation only | SYSGROUP-API-MNT | 2023-05-03 | Announced |
| 195.94.112.0/20 | RIPE | Hub Network Services Ltd | MNT-HNS | 2014-05-23 | Announced |
| 2a01:500::/32 | RIPE | Hub Network Services Ltd | MNT-HNS | 2007-10-13 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS39537 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-AXCENT-T | RIPE | Lists AS39537 as a direct member |
AS-GBLXEU | RIPE | Lists AS39537 as a direct member |
AS-HNS | RIPE | Lists AS39537 as a direct member |
AS-SERVERIUS | RIPE | Lists AS39537 as a direct member |
AS-SYSGROUP | RIPE | Lists AS39537 as a direct member |
AS61180:AS-PEERS-AMSIX | RIPE | Lists AS39537 as a direct member |
RPKI from rpki-client, validated 2026-10-17 12:17 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, collected 2026-10-17. Cross-check on bgp.he.net.