Routing security
AS142641
Unclassified APNIC
Announcements
What this network originates
Every prefix observed with AS142641 as its origin, checked against RPKI and the IRR. Problems sort first.
No announcements from this network were observed in the routing snapshot.
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS142641 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 2406:4440:10::/44 | /48 | APNIC |
| 2602:feda:de0::/44 | /48 | ARIN |
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 AS142641 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 |
|---|---|---|---|---|---|
| 2406:840:ff00::/44 | ALTDB | Yuze Network | MAINT-AS142641 | 2022-04-29 | Not announced |
| 2406:840:ff10::/48 | ALTDB | Yuze Network (Hong Kong) | MAINT-AS142641 | 2022-06-14 | Not announced |
| 2406:840:ff11::/48 | ALTDB | Yuze Network (Taiwan) | MAINT-AS142641 | 2022-06-14 | Not announced |
| 2406:840:ff12::/48 | ALTDB | Yuze Network (Tokyo, Japan) | MAINT-AS142641 | 2022-06-14 | Not announced |
| 2406:840:ff13::/48 | ALTDB | Yuze Network (Singapore) | MAINT-AS142641 | 2022-06-14 | Not announced |
| 2406:840:ff14::/48 | ALTDB | Yuze Network (Los Angeles, United States) | MAINT-AS142641 | 2022-06-14 | Not announced |
| 2406:840:ff15::/48 | ALTDB | Yuze Network (Fremont, United States) | MAINT-AS142641 | 2022-06-14 | Not announced |
| 2406:840:ff1f::/48 | ALTDB | Yuze Network (Frankfurt, German) | MAINT-AS142641 | 2022-06-14 | Not announced |
| 2406:840:ff90::/44 | ALTDB | Yuze Network Tokyo | MAINT-AS142641 | 2025-02-08 | Not announced |
| 2406:4440:10::/48 | ALTDB | Yuze Network | MAINT-AS142641 | 2020-07-04 | Not announced |
| 2406:4440:11::/48 | ALTDB | Yuze Network | MAINT-AS142641 | 2022-04-29 | Not announced |
| 2406:4440:19::/48 | ALTDB | Yuze Network | MAINT-AS142641 | 2020-07-04 | Not announced |
| 2406:4440:1f::/48 | ALTDB | Yuze Network | MAINT-AS142641 | 2021-10-19 | Not announced |
| 2602:feda:de0::/44 | ALTDB | AperNet customer | MNT-APERNET | 2021-08-16 | Not announced |
| 2602:feda:de0::/48 | ALTDB | Yuze Network | MAINT-AS142641 | 2020-07-04 | Not announced |
| 2602:feda:de1::/48 | ALTDB | Yuze Network | MAINT-AS142641 | 2020-07-04 | Not announced |
| 2602:feda:de2::/48 | ALTDB | Yuze Network | MAINT-AS142641 | 2021-11-11 | Not announced |
| 2602:feda:de3::/48 | ALTDB | Yuze Network | MAINT-AS142641 | 2022-04-29 | Not announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS142641 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS-APERNET | APNIC | Lists AS142641 as a direct member |
AS-APERNET-CDN77 | APNIC | Lists AS142641 as a direct member |
AS-APERNET-CTG | ALTDB | Lists AS142641 as a direct member |
AS-BBIX-T-V6 | RADB | Lists AS142641 as a direct member |
AS-KLEYREX-RS | RIPE | Lists AS142641 as a direct member |
AS-MISAKA-CUSTOMERS2 | RIPE | Lists AS142641 as a direct member |
AS-NTZYZ | APNIC | Lists AS142641 as a direct member |
AS140043:AS-HARUUE-PEERS | APNIC | Lists AS142641 as a direct member |
AS142641:AS-ALL | ALTDB | Lists AS142641 as a direct member |
AS146950:AS-PEERINGS | ALTDB | Lists AS142641 as a direct member |
AS63529:AS-63529-AS-IMPORT-AS23764 | APNIC | Lists AS142641 as a direct member |
AS917:AS-CUSTOMERS | ARIN | Lists AS142641 as a direct member |
AS917:AS-CUSTOMERS-LARGE | ARIN | Lists AS142641 as a direct member |
RPKI from rpki-client, validated 2026-10-30 12:03 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-30. Cross-check on bgp.he.net.