Routing security

AS34251 IMC-AS

Residential RIPE

RPKI valid 0% 0 of 23 announcements

RPKI invalid 0 none

No ROA 23 not covered by any ROA

IRR registered 100% 0 missing · 0 other origin

ROAs 0 authorising this AS

Announcements

What this network originates

23 observed

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

Prefix	RPKI	IRR	Vantage points
46.175.16.0/21	No ROA	IRR	56
46.175.16.0/22	No ROA	IRR	56
46.175.16.0/24	No ROA	IRR	56
46.175.17.0/24	No ROA	IRR	56
46.175.18.0/24	No ROA	IRR	56
46.175.19.0/24	No ROA	IRR	56
46.175.20.0/23	No ROA	IRR	56
62.182.120.0/21	No ROA	IRR	57
62.182.122.0/23	No ROA	IRR	56
62.182.125.0/24	No ROA	IRR	13
62.182.126.0/24	No ROA	IRR	13
62.182.127.0/24	No ROA	IRR	13
185.218.198.0/24	No ROA	IRR	56
195.3.128.0/22	No ROA	IRR	51
195.3.128.0/23	No ROA	IRR	13
195.3.128.0/24	No ROA	IRR	13
195.3.129.0/24	No ROA	IRR	13
195.3.130.0/23	No ROA	IRR	13
195.3.130.0/24	No ROA	IRR	13
195.3.131.0/24	No ROA	IRR	13
195.245.120.0/23	No ROA	IRR	57
195.245.120.0/24	No ROA	IRR	51
195.245.121.0/24	No ROA	IRR	51

RPKI · ROAs

Route origin authorisations

0 ROAs

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

No ROA names this AS as an authorised origin.

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

42 objects · 19 not announced

Route objects naming AS34251 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
46.175.16.0/23	RIPE	Network 4/2	`MNT-IMC`	2011-01-31	Not announced
46.175.18.0/23	RIPE	Network 4/5	`MNT-IMC`	2011-01-31	Not announced
46.175.20.0/22	RIPE	Network 4/8	`MNT-IMC`	2011-01-31	Not announced
46.175.20.0/24	RIPE	Network 4/10	`MNT-IMC`	2011-01-31	Not announced
46.175.21.0/24	RIPE	Network 4/11	`MNT-IMC`	2011-01-31	Not announced
46.175.22.0/23	RIPE	Network 4/12	`MNT-IMC`	2011-01-31	Not announced
46.175.22.0/24	RIPE	Network 4/13	`MNT-IMC`	2011-01-31	Not announced
46.175.23.0/24	RIPE	Network 4/14	`MNT-IMC`	2011-01-31	Not announced
62.182.120.0/22	RIPE	Network 5/0	`MNT-IMC`	2008-10-09	Not announced
62.182.120.0/23	RIPE	Network 4/0	`MNT-IMC`	2008-10-09	Not announced
62.182.120.0/24	RIPE	Network 3/0	`MNT-IMC`	2008-10-09	Not announced
62.182.121.0/24	RIPE	Network 3/1	`MNT-IMC`	2008-10-09	Not announced
62.182.122.0/24	RIPE	Network 3/2	`MNT-IMC`	2008-10-09	Not announced
62.182.123.0/24	RIPE	Network 3/3	`MNT-IMC`	2008-10-09	Not announced
62.182.124.0/22	RIPE	Network 5/1	`MNT-IMC`	2008-10-09	Not announced
62.182.124.0/23	RIPE	Network 4/2	`MNT-IMC`	2008-10-09	Not announced
62.182.124.0/24	RIPE	Network 3/4	`MNT-IMC`	2008-10-09	Not announced
62.182.126.0/23	RIPE	Network 4/3	`MNT-IMC`	2008-10-09	Not announced
2001:67c:24a8::/48	RIPE	—	`MNT-IMC`	2020-12-07	Not announced
46.175.16.0/21	RIPE	Network 4/0	`MNT-IMC`	2011-01-31	Announced
46.175.16.0/22	RIPE	Network 4/1	`MNT-IMC`	2011-01-31	Announced
46.175.16.0/24	RIPE	Network 4/3	`MNT-IMC`	2011-01-31	Announced
46.175.17.0/24	RIPE	Network 4/4	`MNT-IMC`	2011-01-31	Announced
46.175.18.0/24	RIPE	Network 4/6	`MNT-IMC`	2011-01-31	Announced
46.175.19.0/24	RIPE	Network 4/7	`MNT-IMC`	2011-01-31	Announced
46.175.20.0/23	RIPE	Network 4/9	`MNT-IMC`	2011-01-31	Announced
62.182.120.0/21	RIPE	imc-net3	`MNT-IMC`	2008-03-17	Announced
62.182.122.0/23	RIPE	Network 4/1	`MNT-IMC`	2008-10-09	Announced
62.182.125.0/24	RIPE	Network 3/5	`MNT-IMC`	2008-10-09	Announced
62.182.126.0/24	RIPE	Network 3/6	`MNT-IMC`	2008-10-09	Announced
62.182.127.0/24	RIPE	Network 3/7	`MNT-IMC`	2008-10-09	Announced
185.218.198.0/24	RIPE	IMC-Net-5	`MNT-IMC`	2021-01-25	Announced
195.3.128.0/22	RIPE	IMC	`MNT-IMC`	2006-07-31	Announced
195.3.128.0/23	RIPE	Network 2/0	`MNT-IMC`	2008-10-09	Announced
195.3.128.0/24	RIPE	Network 1/0	`MNT-IMC`	2008-10-09	Announced
195.3.129.0/24	RIPE	Network 1/1	`MNT-IMC`	2008-10-09	Announced
195.3.130.0/23	RIPE	Network 2/1	`MNT-IMC`	2008-10-09	Announced
195.3.130.0/24	RIPE	Network 1/3	`MNT-IMC`	2008-10-09	Announced
195.3.131.0/24	RIPE	Network 1/4	`MNT-IMC`	2008-10-09	Announced
195.245.120.0/23	RIPE	IMC	`MNT-IMC`	2006-07-31	Announced
195.245.120.0/24	RIPE	Network 0/0	`MNT-IMC`	2008-10-09	Announced
195.245.121.0/24	RIPE	Network 0/0	`MNT-IMC`	2008-10-09	Announced

IRR

AS-sets

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

AS-set	Where	Relationship
`AS-BORIX`	RIPE	Lists AS34251 as a direct member
`AS-HLS`	RIPE	Lists AS34251 as a direct member
`AS-HURRICANE`	RADB	Lists AS34251 as a direct member
`AS-IMC`	RIPE	Lists AS34251 as a direct member
`AS-IMC-DATAGROUP`	RIPE	Lists AS34251 as a direct member
`AS-IMC-UA`	RIPE	Lists AS34251 as a direct member
`AS-IMC-UARNET`	RIPE	Lists AS34251 as a direct member
`AS-RETN-ACTUAL-V4`	RIPE	Lists AS34251 as a direct member
`AS-TRANSROUTE-SPEC`	RIPE	Lists AS34251 as a direct member
`AS-UARNET`	RIPE	Lists AS34251 as a direct member

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