Routing security
AS35487 MISAKA
Unclassified RIPE
RPKI valid
77%
54 of 70 announcements
RPKI invalid
1
dropped by validating networks
No ROA
15
not covered by any ROA
IRR registered
81%
12 missing · 1 other origin
ROAs
17
authorising this AS
Announcements
What this network originates
Every prefix observed with AS35487 as its origin, checked against RPKI and the IRR. Problems sort first.
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS35487 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 45.85.121.0/24 | /24 | RIPENCC |
| 45.131.68.0/22 | /24 | RIPENCC |
| 45.134.168.0/23 | /24 | RIPENCC |
| 45.142.247.0/24 | /24 | RIPENCC |
| 45.150.240.0/23 | /24 | RIPENCC |
| 45.150.243.0/24 | /24 | RIPENCC |
| 146.19.3.0/24 | /24 | RIPENCC |
| 177.177.0.0/19 | /32 | RIPENCC |
| 194.156.154.0/24 | /24 | RIPENCC |
| 201.50.0.0/20 | /32 | RIPENCC |
| 2a0b:4341::/32 | /48 | RIPENCC |
| 2a0b:4342:1a90::/44 | /48 | RIPENCC |
| 2a0d:5641:1a00::/40 | /48 | RIPENCC |
| 2a0d:5642::/32 | /48 | RIPENCC |
| 2a0f:3b05:100::/44 | /44 | RIPENCC |
| 2a12:1701::/32 | /48 | RIPENCC |
| 2a12:8d02::/32 | /48 | 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 AS35487 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 |
|---|---|---|---|---|---|
| 45.134.169.0/24 | RIPE | — | XTOM | 2026-04-02 | Not announced |
| 177.177.19.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Not announced |
| 177.177.24.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Not announced |
| 177.177.28.0/24 | RIPE | — | MISAKA-MNT | 2026-06-29 | Not announced |
| 201.78.142.0/24 | RIPE | — | MISAKA-MNT | 2026-05-17 | Not announced |
| 201.78.146.0/24 | RIPE | — | MISAKA-MNT | 2026-05-09 | Not announced |
| 201.78.147.0/24 | RIPE | — | MISAKA-MNT | 2026-05-09 | Not announced |
| 201.78.148.0/24 | RIPE | — | MISAKA-MNT | 2026-05-09 | Not announced |
| 201.78.149.0/24 | RIPE | — | MISAKA-MNT | 2026-05-09 | Not announced |
| 201.78.150.0/24 | RIPE | — | MISAKA-MNT | 2026-05-09 | Not announced |
| 201.78.151.0/24 | RIPE | — | MISAKA-MNT | 2026-05-09 | Not announced |
| 201.78.152.0/24 | RIPE | — | MISAKA-MNT | 2026-05-09 | Not announced |
| 201.78.153.0/24 | RIPE | — | MISAKA-MNT | 2026-05-09 | Not announced |
| 201.78.154.0/24 | RIPE | — | MISAKA-MNT | 2026-05-09 | Not announced |
| 2a0b:4342:1a90::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2023-11-27 | Not announced |
| 2a0d:5642::/32 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2020-04-24 | Not announced |
| 2a0d:5642:106::/48 | RIPE | Misaka.io Edge Infrastructure in Belgrade, Serbia | MISAKA-MNT | 2022-10-24 | Not announced |
| 2a0d:5642:113::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2019-04-16 | Not announced |
| 2a0d:5642:119::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2020-04-24 | Not announced |
| 2a0d:5642:121::/48 | RIPE | Misaka.io Edge Infrastructure in Budapest, Hungary | MISAKA-MNT | 2022-10-24 | Not announced |
| 2a0d:5642:124::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2019-04-22 | Not announced |
| 2a0d:5642:125::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2019-07-12 | Not announced |
| 2a0d:5642:126::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2019-07-29 | Not announced |
| 2a0d:5642:128::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2020-04-24 | Not announced |
| 2a0d:5642:129::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2020-10-02 | Not announced |
| 2a0d:5642:131::/48 | RIPE | Misaka.io Edge Infrastucture in Lisbon, Portugal | MISAKA-MNT | 2023-09-06 | Not announced |
| 2a0d:5642:132::/48 | RIPE | Misaka.io Edge Infrastucture in Zagreb, Croatia | MISAKA-MNT | 2023-09-06 | Not announced |
| 2a0d:5642:1a30::/44 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2021-03-25 | Not announced |
| 2a0f:3b05::/32 | RIPE | — | MISAKA-MNT | 2022-03-17 | Not announced |
| 2a12:1701::/40 | RIPE | — | MISAKA-MNT | 2022-05-01 | Not announced |
| 2a12:1701:100::/40 | RIPE | — | MISAKA-MNT | 2022-05-01 | Not announced |
| 2a12:8d01::/32 | RIPE | — | MISAKA-MNT | 2026-04-07 | Not announced |
| 2a12:8d01:ee13::/48 | RIPE | — | MISAKA-MNT | 2026-04-07 | Not announced |
| 45.85.121.0/24 | RIPE | — | MISAKA-MNT | 2026-05-09 | Announced |
| 45.131.71.0/24 | RIPE | — | MISAKA-MNT | 2023-01-06 | Announced |
| 45.134.168.0/24 | RIPE | — | XTOM | 2026-04-02 | Announced |
| 45.142.247.0/24 | RIPE | — | MISAKA-MNT | 2023-01-06 | Announced |
| 45.150.240.0/24 | RIPE | — | MISAKA-MNT | 2022-03-16 | Announced |
| 45.150.241.0/24 | RIPE | — | MISAKA-MNT | 2023-05-17 | Announced |
| 45.150.243.0/24 | RIPE | — | MISAKA-MNT | 2022-02-02 | Announced |
| 102.130.48.0/24 | AFRINIC | Customer Route | XL1-MNT | 2022-11-08 | Announced |
| 102.130.48.0/24 | RADB | Misaka Network Customer Prefix | MAINT-AS9312 | 2023-11-13 | Announced |
| 102.130.49.0/24 | AFRINIC | Customer Route | XL1-MNT | 2022-11-08 | Announced |
| 102.130.49.0/24 | RADB | Misaka.IO JNB01 | MAINT-AS9312 | 2023-11-13 | Announced |
| 146.19.3.0/24 | RIPE | — | MISAKA-MNT | 2022-05-01 | Announced |
| 177.177.0.0/23 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.2.0/23 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.12.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.13.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.14.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.15.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.16.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.18.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.20.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.21.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.22.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.23.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.25.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.26.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.27.0/24 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 177.177.30.0/24 | RIPE | — | MISAKA-MNT | 2026-08-26 | Announced |
| 177.177.31.0/24 | RIPE | — | MISAKA-MNT | 2026-08-26 | Announced |
| 194.156.154.0/24 | RIPE | — | MISAKA-MNT | 2024-02-27 | Announced |
| 201.50.0.0/23 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 201.50.2.0/23 | RIPE | — | MISAKA-MNT | 2026-06-24 | Announced |
| 2a0b:4341:2e00::/48 | RIPE | — | MISAKA-MNT | 2021-12-30 | Announced |
| 2a0b:4342:1a90::/44 | RIPE | Misaka.io Customer Infrastructure in Johannesburg, South Africa | MISAKA-MNT | 2023-12-20 | Announced |
| 2a0d:5641:1a00::/40 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2021-03-26 | Announced |
| 2a0d:5642:101::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2022-01-27 | Announced |
| 2a0d:5642:104::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2020-04-24 | Announced |
| 2a0d:5642:105::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2021-01-14 | Announced |
| 2a0d:5642:107::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2020-04-24 | Announced |
| 2a0d:5642:110::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2020-04-15 | Announced |
| 2a0d:5642:112::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2020-01-13 | Announced |
| 2a0d:5642:115::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2020-04-15 | Announced |
| 2a0d:5642:116::/48 | RIPE | Misaka.io Edge Infrastucture in Copenhagen, Denmark | MISAKA-MNT | 2022-10-24 | Announced |
| 2a0d:5642:117::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2020-01-13 | Announced |
| 2a0d:5642:130::/48 | RIPE | Misaka.io Edge Infrastucture in Marseille, France | MISAKA-MNT | 2023-09-06 | Announced |
| 2a0d:5642:140::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2022-04-28 | Announced |
| 2a0d:5642:150::/48 | RIPE | Misaka.io Edge Infrastucture in Athens, Greece | MISAKA-MNT | 2023-09-06 | Announced |
| 2a0d:5642:151::/48 | RIPE | Misaka.io Edge Infrastucture in Lisbon, Portugal | MISAKA-MNT | 2023-09-06 | Announced |
| 2a0d:5642:152::/48 | RIPE | Misaka.io Edge Infrastucture in Zagreb, Croatia | MISAKA-MNT | 2023-09-06 | Announced |
| 2a0d:5642:153::/48 | RIPE | Misaka.io Edge Infrastucture in Warsaw, Poland | MISAKA-MNT | 2023-09-15 | Announced |
| 2a0d:5642:201::/48 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2022-02-02 | Announced |
| 2a0f:3b05:100::/44 | RIPE | — | MISAKA-MNT | 2022-03-17 | Announced |
| 2a11:6e03::/32 | RIPE | Misaka Network, Inc. | MISAKA-MNT | 2026-02-10 | Announced |
| 2a12:8d02::/32 | RIPE | — | MISAKA-MNT | 2023-01-06 | Announced |
| 2a12:8d02:2000::/36 | RIPE | — | MISAKA-MNT | 2023-01-06 | Announced |
| 2a12:8d02:2010::/48 | RIPE | — | MISAKA-MNT | 2023-06-12 | Announced |
| 2a12:8d02:21b0::/48 | RIPE | Misaka.io Berlin Speedtest Servers | MISAKA-MNT | 2024-05-15 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS35487 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-CLUESONIT | RIPE | Lists AS35487 as a direct member |
AS-DURAND1-CUSTOMER | RADB | Lists AS35487 as a direct member |
AS-GBXSCUST-FULL | RIPE | Lists AS35487 as a direct member |
AS-GIGAINFRA | RADB | Lists AS35487 as a direct member |
AS-HYONIX | RIPE | Lists AS35487 as a direct member |
AS-IIJ | RADB | Lists AS35487 as a direct member |
AS-MISAKA-CORE | RIPE | Lists AS35487 as a direct member |
AS-MISAKA-CUSTOMERS2 | RIPE | Lists AS35487 as a direct member |
AS-NWN-TRANSIT | RADB | Lists AS35487 as a direct member |
AS-RETN-ACTUAL-V4 | RIPE | Lists AS35487 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS35487 as a direct member |
AS-TRANSROUTE-SPEC | RIPE | Lists AS35487 as a direct member |
AS-TTNET | RIPE | Lists AS35487 as a direct member |
AS-TURKTELEKOM | RIPE | Lists AS35487 as a direct member |
AS-XTOM-CUSTOMERS | ALTDB | Lists AS35487 as a direct member |
AS-XTOM-CUSTOMERS | RADB | Lists AS35487 as a direct member |
AS-XTOM-CUSTOMERS | RIPE | Lists AS35487 as a direct member |
AS137409:AS-MERCURY | RADB | Lists AS35487 as a direct member |
AS2497:AS-IIJ | RADB | Lists AS35487 as a direct member |
AS3214:AS-FILTERED | ALTDB | Lists AS35487 as a direct member |
AS3214:AS-FILTERED | RADB | Lists AS35487 as a direct member |
AS3214:AS-FILTERED | RIPE | Lists AS35487 as a direct member |
AS3491:AS-CUSTOMERS-AP | RADB | Lists AS35487 as a direct member |
AS917:AS-CORE | ARIN | Lists AS35487 as a direct member |
AS917:AS-CUSTOMERS | ARIN | Lists AS35487 as a direct member |
AS917:AS-OWN | ARIN | Lists AS35487 as a direct member |
RPKI from rpki-client, validated 2026-10-12 12:10 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-12. Cross-check on bgp.he.net.