Routing security

AS51469 Petiak Petiak System Co JSC

Unclassified RIPE

RPKI valid 100% 17 of 17 announcements

RPKI invalid 0 none

No ROA 0 not covered by any ROA

IRR registered 100% 0 missing · 0 other origin

ROAs 17 authorising this AS

Announcements

What this network originates

17 observed

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

Prefix	RPKI	IRR	Vantage points
2a00:6380::/32	RPKI valid	IRR	32
31.171.216.0/23	RPKI valid	IRR	54
31.171.218.0/23	RPKI valid	IRR	54
31.171.220.0/23	RPKI valid	IRR	54
31.171.222.0/23	RPKI valid	IRR	54
185.16.232.0/23	RPKI valid	IRR	54
185.16.234.0/23	RPKI valid	IRR	54
217.170.240.0/23	RPKI valid	IRR	54
217.170.242.0/23	RPKI valid	IRR	54
217.170.244.0/23	RPKI valid	IRR	54
217.170.244.0/24	RPKI valid	IRR	54
217.170.245.0/24	RPKI valid	IRR	54
217.170.246.0/23	RPKI valid	IRR	54
217.170.248.0/23	RPKI valid	IRR	54
217.170.250.0/23	RPKI valid	IRR	54
217.170.252.0/23	RPKI valid	IRR	54
217.170.254.0/23	RPKI valid	IRR	54

RPKI · ROAs

Route origin authorisations

17 ROAs

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

Prefix	Max length	Trust anchor
31.171.216.0/23	/23	RIPENCC
31.171.218.0/23	/23	RIPENCC
31.171.220.0/23	/23	RIPENCC
31.171.222.0/23	/23	RIPENCC
185.16.232.0/23	/23	RIPENCC
185.16.234.0/23	/23	RIPENCC
217.170.240.0/23	/23	RIPENCC
217.170.242.0/23	/23	RIPENCC
217.170.244.0/23	/23	RIPENCC
217.170.244.0/24	/24	RIPENCC
217.170.245.0/24	/24	RIPENCC
217.170.246.0/23	/23	RIPENCC
217.170.248.0/23	/23	RIPENCC
217.170.250.0/23	/23	RIPENCC
217.170.252.0/23	/23	RIPENCC
217.170.254.0/23	/23	RIPENCC
2a00:6380::/32	/32	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

40 objects · 19 not announced

Route objects naming AS51469 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
5.160.116.0/22	RIPE	Petiak Route	`MNT-RSPN`	2017-03-06	Not announced
5.160.144.0/23	RIPE	Petiak Route	`MNT-RSPN`	2015-11-11	Not announced
5.202.168.0/21	RIPE	—	`PTE-MNT`	2021-04-10	Not announced
31.171.216.0/21	RIPE	Petiak Network	`MNT-PETIAK`	2014-01-20	Not announced
31.171.216.0/22	RIPE	Petiak Network	`MNT-PETIAK`	2014-01-18	Not announced
31.171.220.0/22	RIPE	Petiak Network	`MNT-PETIAK`	2011-10-02	Not announced
81.31.224.0/22	RIPE	—	`CHAPAR-MNT`	2025-02-24	Not announced
81.31.228.0/23	RIPE	—	`CHAPAR-MNT`	2025-02-24	Not announced
81.31.236.0/22	RIPE	—	`CHAPAR-MNT`	2025-02-24	Not announced
81.31.240.0/23	RIPE	—	`CHAPAR-MNT`	2025-02-24	Not announced
81.31.248.0/23	RIPE	—	`CHAPAR-MNT`	2025-02-24	Not announced
185.16.232.0/22	RIPE	Petiak Network	`MNT-PETIAK`	2013-01-25	Not announced
217.170.240.0/20	RIPE	Petiak Network	`MNT-PETIAK`	2011-04-26	Not announced
217.170.240.0/21	RIPE	Petiak Route	`MNT-PETIAK`	2012-04-05	Not announced
217.170.240.0/22	RIPE	Petiak Network	`MNT-PETIAK`	2012-04-15	Not announced
217.170.244.0/22	RIPE	Petiak Network	`MNT-PETIAK`	2012-04-15	Not announced
217.170.248.0/21	RIPE	Petiak Route	`MNT-PETIAK`	2012-04-05	Not announced
217.170.248.0/22	RIPE	Petiak Network	`MNT-PETIAK`	2013-03-05	Not announced
217.170.252.0/22	RIPE	Petiak Network	`MNT-PETIAK`	2013-03-05	Not announced
31.171.216.0/23	RADB	GBI via EMIX	`MAINT-AS8966`	2023-11-13	Announced
31.171.216.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
31.171.218.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
31.171.220.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
31.171.222.0/23	RADB	GBI via EMIX	`MAINT-AS8966`	2023-11-13	Announced
31.171.222.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
185.16.232.0/23	RADB	GBI via EMIX	`MAINT-AS8966`	2023-11-13	Announced
185.16.232.0/23	RIPE	Petiak PPPOE Pool	`MNT-PETIAK`	2014-12-10	Announced
185.16.234.0/23	RADB	GBI via EMIX	`MAINT-AS8966`	2023-11-13	Announced
185.16.234.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
217.170.240.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
217.170.242.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
217.170.244.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
217.170.244.0/24	RIPE	—	`MNT-PETIAK`	2024-04-20	Announced
217.170.245.0/24	RIPE	—	`MNT-PETIAK`	2024-04-20	Announced
217.170.246.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
217.170.248.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
217.170.250.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2014-12-14	Announced
217.170.252.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2013-03-14	Announced
217.170.254.0/23	RIPE	Petiak Route	`MNT-PETIAK`	2013-03-14	Announced
2a00:6380::/32	RIPE	Petiak IPv6 Route	`MNT-PETIAK`	2011-04-29	Announced

IRR

AS-sets

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

AS-set	Where	Relationship
`AS-AF81NET`	RIPE	Lists AS51469 as a direct member
`AS-ASIATECH`	RIPE	Lists AS51469 as a direct member
`AS-AZAD24NET`	RIPE	Lists AS51469 as a direct member
`AS-DCI`	RIPE	Lists AS51469 as a direct member
`AS-EMIX`	RADB	Lists AS51469 as a direct member
`AS-HURRICANEV6`	RADB	Lists AS51469 as a direct member
`AS-IR-ASN`	RIPE	Lists AS51469 as a direct member
`AS-LASER`	RIPE	Lists AS51469 as a direct member
`AS-NETASSIST`	RIPE	Lists AS51469 as a direct member
`AS-NSST`	RIPE	Lists AS51469 as a direct member
`AS-RESPINA`	RIPE	Lists AS51469 as a direct member
`AS-TICGW`	RIPE	Lists AS51469 as a direct member
`AS-UKRAINE`	RIPE	Lists AS51469 as a direct member
`AS34984:AS-TELLCOM`	RIPE	Lists AS51469 as a direct member
`AS41194:AS-RASCOM`	RIPE	Lists AS51469 as a direct member

RPKI from rpki-client, validated 2026-11-02 13:01 UTC. IRR from ARIN, RADB, RIPE, ALTDB, APNIC, LACNIC, NTTCOM, AFRINIC, collected 2026-11-02. Cross-check on bgp.he.net.