Routing security
AS209300 TWD2-NET TWD2 Education and Research Network
Unclassified RIPE Educational/Research
Announcements
What this network originates
Every prefix observed with AS209300 as its origin, checked against RPKI and the IRR. Problems sort first.
| Prefix | RPKI | IRR | Vantage points |
|---|---|---|---|
| 44.30.120.0/24 | No ROA | IRR | 54 |
| 2a0c:b641:573::/48 | RPKI valid | IRR covering | 31 |
| 2a05:1085::/32 | RPKI valid | IRR | 31 |
| 2404:f4c0:f000::/44 | RPKI valid | IRR | 19 |
| 2404:f4c0:f001::/48 | RPKI valid | IRR | 31 |
| 2404:f4c0:f002::/48 | RPKI valid | IRR | 31 |
RPKI · ROAs
Route origin authorisations
Signed statements by address holders that AS209300 may originate these prefixes, up to the maximum length shown.
| Prefix | Max length | Trust anchor |
|---|---|---|
| 2404:f4c0:f000::/44 | /48 | APNIC |
| 2a05:1085::/32 | /48 | RIPENCC |
| 2a0c:b641:570::/44 | /48 | RIPENCC |
| 2a0e:aa06:490::/44 | /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 |
|---|---|---|---|
| AS4842 | Tianhai InfoTech | Declared | not observed |
| AS6939 | Hurricane Electric LLC | Declared | not observed |
| AS8772 | Netassist International EOOD | Declared | Observed |
| AS20473 | The Constant Company, LLC | Declared | Observed |
| AS24239 | TWD2 Education and Research Network | Declared | not observed |
| AS29632 | Netassist International EOOD | Declared | Observed |
| AS38255 | China Education and Research Network (CERNET) | Declared | Observed |
| AS45576 | Tsinghua University | Declared | Observed |
| AS142650 | China Education and Research Network (CERNET) | Declared | Observed |
| AS212683 | Olilo UK & Ireland Ltd. | Declared | Observed |
| AS37989 | DCS1 Pte. Ltd. | not declared | Observed |
| AS58057 | Securebit AG | 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 AS209300 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 |
|---|---|---|---|---|---|
| 2404:f4c0:f000::/45 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f000::/46 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f000::/47 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f000::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f002::/47 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f003::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f004::/46 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f004::/47 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f004::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f005::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f006::/47 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f006::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f007::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f008::/45 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f008::/46 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f008::/47 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f008::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f009::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f00a::/47 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f00a::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f00b::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f00c::/46 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f00c::/47 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f00c::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f00d::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f00e::/47 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f00e::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2404:f4c0:f00f::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Not announced |
| 2a0c:b641:570::/44 | RADB | Vultr Customer Route | MAINT-AS20473 | 2026-09-26 | Not announced |
| 2a0c:b641:570::/44 | RIPE | — | TWD2-MNT | 2019-03-01 | Not announced |
| 2a0e:aa06:490::/44 | RIPE | — | TIANHAI-MNT | 2020-02-25 | Not announced |
| 2a0e:aa06:49f::/48 | RIPE | — | TWD2-MNT | 2024-04-26 | Not announced |
| 2a0e:b107:740::/44 | RIPE | — | TWD2-MNT | 2020-03-30 | Not announced |
| 44.30.120.0/24 | RADB | M0THU | MAINT-ARDC | 2026-02-27 | Announced |
| 2404:f4c0:f000::/44 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-13 | Announced |
| 2404:f4c0:f000::/44 | RADB | Vultr Customer Route | MAINT-AS20473 | 2023-11-13 | Announced |
| 2404:f4c0:f001::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Announced |
| 2404:f4c0:f002::/48 | APNIC | Wuhan LSHIY Network Technology Co., Ltd. | MAINT-LSHIY-CN | 2019-06-16 | Announced |
| 2a05:1085::/32 | RIPE | — | TWD2-MNT | 2021-06-08 | Announced |
IRR
AS-sets
The as-set is what upstreams expand to build this network's customer filter. Sets that list AS209300 directly show who expects to carry it.
| AS-set | Where | Relationship |
|---|---|---|
AS209300:AS-CUSTOMERS | PeeringDB | Declared by the operator as its own set |
AS-4IXP | RIPE | Lists AS209300 as a direct member |
AS-4IXP-RS | RIPE | Lists AS209300 as a direct member |
AS-4IXPV6 | RIPE | Lists AS209300 as a direct member |
AS-EVIX | ALTDB | Lists AS209300 as a direct member |
AS-RETN-ACTUAL-V6 | RIPE | Lists AS209300 as a direct member |
AS-TWD2-NET | APNIC | Lists AS209300 as a direct member |
AS20473:AS-VULTR | RADB | Lists AS209300 as a direct member |
AS209300:AS-CUSTOMERS | RIPE | Lists AS209300 as a direct member |
AS212683:AS-OLILO | RIPE | Lists AS209300 as a direct member |
AS4842:AS-DOWNSTREAMS | APNIC | Lists AS209300 as a direct member |
RPKI from rpki-client, validated 2026-10-29 12:01 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-29. Cross-check on bgp.he.net.