Routing security

AS401163 ACGNODE

Unclassified ARIN

RPKI valid 83% 45 of 54 announcements

RPKI invalid 0 none

No ROA 9 not covered by any ROA

IRR registered 74% 14 missing · 0 other origin

ROAs 37 authorising this AS

Announcements

What this network originates

54 observed

Every prefix observed with AS401163 as its origin, checked against RPKI and the IRR. Problems sort first.

Prefix	RPKI	IRR	Vantage points
61.97.249.0/24	No ROA	IRR	54
103.86.84.0/24	No ROA	IRR	54
103.86.86.0/24	No ROA	IRR	54
103.101.189.0/24	No ROA	IRR	54
103.138.80.0/24	No ROA	IRR	54
103.138.81.0/24	No ROA	IRR	51
103.138.82.0/24	No ROA	IRR	54
103.138.83.0/24	No ROA	IRR	54
103.140.220.0/24	No ROA	IRR	54
2a12:28c0::/33	RPKI valid	No IRR	34
2a12:28c0:8000::/33	RPKI valid	No IRR	34
2a12:28c1::/33	RPKI valid	No IRR	34
2a12:28c1:8000::/33	RPKI valid	No IRR	34
2a12:28c2::/33	RPKI valid	No IRR	34
2a12:28c2:8000::/33	RPKI valid	No IRR	34
2a12:28c3::/33	RPKI valid	No IRR	34
2a12:28c3:8000::/33	RPKI valid	No IRR	34
2a14:e01::/33	RPKI valid	No IRR	34
2a14:e01:8000::/33	RPKI valid	No IRR	34
2a14:e02::/33	RPKI valid	No IRR	34
2a14:e02:8000::/33	RPKI valid	No IRR	34
2a14:e03::/33	RPKI valid	No IRR	34
2a14:e03:8000::/33	RPKI valid	No IRR	34
2a0b:d900::/33	RPKI valid	IRR covering	34
2a0b:d900:8000::/33	RPKI valid	IRR covering	34
2a0b:d901::/33	RPKI valid	IRR covering	34
2a0b:d901:8000::/33	RPKI valid	IRR covering	34
2a0b:d902::/33	RPKI valid	IRR covering	34
2a0b:d902:8000::/33	RPKI valid	IRR covering	34
2a0b:d903::/33	RPKI valid	IRR covering	34
2a0b:d903:8000::/33	RPKI valid	IRR covering	34
2a0f:7c80::/29	RPKI valid	IRR	31
2a0f:a500::/29	RPKI valid	IRR	31
2a10:bc40::/33	RPKI valid	IRR covering	34
2a10:bc40:8000::/33	RPKI valid	IRR covering	34
2a10:dbc1::/33	RPKI valid	IRR covering	34
2a10:dbc1:8000::/33	RPKI valid	IRR covering	34
2a10:dbc2::/33	RPKI valid	IRR covering	34
2a10:dbc2:8000::/33	RPKI valid	IRR covering	34
2a10:dbc3::/33	RPKI valid	IRR covering	34
2a10:dbc3:8000::/33	RPKI valid	IRR covering	34
2a10:dbc4::/33	RPKI valid	IRR covering	34
2a10:dbc4:8000::/33	RPKI valid	IRR covering	34
2a10:dbc5::/33	RPKI valid	IRR covering	34
2a10:dbc5:8000::/33	RPKI valid	IRR covering	34
2a10:dbc6::/33	RPKI valid	IRR covering	34
2a10:dbc6:8000::/33	RPKI valid	IRR covering	34
2a10:dbc7::/33	RPKI valid	IRR covering	34
2a10:dbc7:8000::/33	RPKI valid	IRR covering	34
2a11:c944::/33	RPKI valid	IRR covering	34
2a11:c944:8000::/33	RPKI valid	IRR covering	34
2a12:5f42::/33	RPKI valid	IRR covering	34
2a12:5f42:8000::/33	RPKI valid	IRR covering	34
2a14:4a80::/29	RPKI valid	IRR	31

RPKI · ROAs

Route origin authorisations

37 ROAs

Signed statements by address holders that AS401163 may originate these prefixes, up to the maximum length shown.

Prefix	Max length	Trust anchor
2a00:e460::/29	/48	RIPENCC
2a06:cac0::/29	/48	RIPENCC
2a0b:9800::/29	/48	RIPENCC
2a0b:a280::/29	/48	RIPENCC
2a0b:d900::/29	/48	RIPENCC
2a0c:65c0::/29	/48	RIPENCC
2a0c:6980::/29	/48	RIPENCC
2a0d:b140::/29	/48	RIPENCC
2a0f:1180::/29	/48	RIPENCC
2a0f:2380::/29	/48	RIPENCC
2a0f:4680::/29	/48	RIPENCC
2a0f:7c80::/29	/29	RIPENCC
2a0f:9fc0::/29	/48	RIPENCC
2a0f:a500::/29	/29	RIPENCC
2a10:bc40::/29	/48	RIPENCC
2a10:dbc0::/29	/48	RIPENCC
2a11:9600::/29	/48	RIPENCC
2a11:c940::/29	/48	RIPENCC
2a12:ec0::/29	/48	RIPENCC
2a12:1900::/29	/48	RIPENCC
2a12:28c0::/29	/48	RIPENCC
2a12:5f40::/29	/48	RIPENCC
2a13:97c0::/29	/48	RIPENCC
2a13:9ac0::/29	/48	RIPENCC
2a13:a740::/29	/48	RIPENCC
2a13:e8c0::/29	/48	RIPENCC
2a14:e00::/29	/48	RIPENCC
2a14:1040::/29	/29	RIPENCC
2a14:15c0::/29	/29	RIPENCC
2a14:16c0::/29	/29	RIPENCC
2a14:1740::/29	/29	RIPENCC
2a14:1bc0::/29	/29	RIPENCC
2a14:1c40::/29	/29	RIPENCC
2a14:1cc0::/29	/29	RIPENCC
2a14:1d40::/29	/29	RIPENCC
2a14:4600::/29	/48	RIPENCC
2a14:4a80::/29	/29	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

29 objects · 17 not announced

Route objects naming AS401163 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
49.128.219.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Not announced
103.86.84.0/22	RADB	—	`MAINT-AS55201`	2025-09-02	Not announced
103.101.188.0/22	RADB	—	`MAINT-AS55201`	2025-09-02	Not announced
103.101.190.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Not announced
103.131.167.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Not announced
112.196.203.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Not announced
2a00:e460::/29	RIPE	client2	`NETWORK-SUPPORT-MNT`	2025-12-24	Not announced
2a0b:d900::/29	RIPE	client2	`NETWORK-SUPPORT-MNT`	2025-12-24	Not announced
2a0c:65c0::/29	RIPE	client2	`NETWORK-SUPPORT-MNT`	2025-12-24	Not announced
2a0c:6980::/29	RIPE	client2	`NETWORK-SUPPORT-MNT`	2025-12-24	Not announced
2a0d:b140::/29	RIPE	—	`IPSERVICES-MNT`	2026-06-16	Not announced
2a10:bc40::/29	RIPE	—	`IPSERVICES-MNT`	2026-06-16	Not announced
2a10:dbc0::/29	RIPE	—	`IP-SERVICES-MNT`	2026-09-12	Not announced
2a11:c940::/29	RIPE	—	`DEMENIN-MNT`	2026-06-16	Not announced
2a12:4900::/29	RIPE	swains	`D2CLOUD-ZA-MNT`	2026-08-08	Not announced
2a12:5f40::/29	RIPE	—	`IPSERVICES-MNT`	2026-06-16	Not announced
2a13:97c0::/29	RIPE	client2	`NETWORK-SUPPORT-MNT`	2025-12-24	Not announced
61.97.249.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Announced
103.86.84.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Announced
103.86.86.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Announced
103.101.189.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Announced
103.138.80.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Announced
103.138.81.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Announced
103.138.82.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Announced
103.138.83.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Announced
103.140.220.0/24	RADB	—	`MAINT-AS55201`	2025-09-02	Announced
2a0f:7c80::/29	RIPE	IPv4Center.com Lease Route	`IPV4CENTER-MNT`	2026-08-31	Announced
2a0f:a500::/29	RIPE	IPv4Center.com Lease Route	`IPV4CENTER-MNT`	2026-08-31	Announced
2a14:4a80::/29	RIPE	IPv4Center.com Lease Route	`IPV4CENTER-MNT`	2026-08-31	Announced

IRR

AS-sets

The as-set is what upstreams expand to build this network's customer filter. Sets that list AS401163 directly show who expects to carry it.

AS-set	Where	Relationship
`AS-CLOUDIE-HK`	RADB	Lists AS401163 as a direct member
`AS-HURRICANE`	RADB	Lists AS401163 as a direct member
`AS-HURRICANEV6`	RADB	Lists AS401163 as a direct member
`AS-SKBROADBAND`	RADB	Lists AS401163 as a direct member
`AS-SKYQUANTUM:AS-INTERNET-SERVICE`	RADB	Lists AS401163 as a direct member
`AS-ZENLAYER`	RADB	Lists AS401163 as a direct member
`AS58453:AS-ASIAASCUST`	APNIC	Lists AS401163 as a direct member
`AS58453:AS-ASIAASCUST`	RADB	Lists AS401163 as a direct member

RPKI from rpki-client, validated 2026-10-14 12:07 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-10-14. Cross-check on bgp.he.net.