Routing security

AS44507 KMTN-AS

Unclassified RIPE

RPKI valid 100% 18 of 18 announcements

RPKI invalid 0 none

No ROA 0 not covered by any ROA

IRR registered 100% 0 missing · 0 other origin

ROAs 19 authorising this AS

Announcements

What this network originates

18 observed

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

Prefix	RPKI	IRR	Vantage points
5.175.88.0/21	RPKI valid	IRR	51
46.42.0.0/18	RPKI valid	IRR	51
46.42.16.0/21	RPKI valid	IRR	51
46.42.24.0/21	RPKI valid	IRR	51
46.42.32.0/21	RPKI valid	IRR	51
46.42.40.0/21	RPKI valid	IRR	51
46.42.48.0/21	RPKI valid	IRR	52
46.42.56.0/21	RPKI valid	IRR	52
46.228.96.0/20	RPKI valid	IRR	51
134.90.152.0/21	RPKI valid	IRR	51
146.247.32.0/21	RPKI valid	IRR	51
178.57.32.0/21	RPKI valid	IRR	51
178.57.40.0/21	RPKI valid	IRR	51
178.57.48.0/21	RPKI valid	IRR	51
185.16.56.0/22	RPKI valid	IRR	51
188.120.48.0/20	RPKI valid	IRR	51
194.58.160.0/21	RPKI valid	IRR	51
194.58.176.0/21	RPKI valid	IRR	51

RPKI · ROAs

Route origin authorisations

19 ROAs

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

Prefix	Max length	Trust anchor
5.175.88.0/21	/21	RIPENCC
46.42.0.0/18	/18	RIPENCC
46.42.8.0/21	/21	RIPENCC
46.42.16.0/21	/21	RIPENCC
46.42.24.0/21	/21	RIPENCC
46.42.32.0/21	/21	RIPENCC
46.42.40.0/21	/21	RIPENCC
46.42.48.0/21	/21	RIPENCC
46.42.56.0/21	/21	RIPENCC
46.228.96.0/20	/20	RIPENCC
134.90.152.0/21	/21	RIPENCC
146.247.32.0/21	/21	RIPENCC
178.57.32.0/21	/21	RIPENCC
178.57.40.0/21	/21	RIPENCC
178.57.48.0/21	/21	RIPENCC
185.16.56.0/22	/22	RIPENCC
188.120.48.0/20	/20	RIPENCC
194.58.160.0/21	/21	RIPENCC
194.58.176.0/21	/21	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

33 objects · 14 not announced

Route objects naming AS44507 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.42.0.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2010-11-18	Not announced
46.42.8.0/21	RIPE	Users ADSL/HFE	`KMTN2-MNT`	2010-12-21	Not announced
46.42.24.0/22	RIPE	OAO KGTS	`KMTN2-MNT`	2010-11-18	Not announced
46.42.28.0/22	RIPE	OJSC Kostroma Municipal Telephone Network adsl users segment	`KMTN2-MNT`	2010-08-12	Not announced
46.42.32.0/22	RIPE	OAO KGTS adsl users segment	`KMTN2-MNT`	2010-11-23	Not announced
46.42.36.0/22	RIPE	OJSC Kostroma Municipal Telephone Network adsl users segment	`KMTN2-MNT`	2010-08-12	Not announced
46.42.40.0/22	RIPE	OAO KGTS adsl users segment	`KMTN2-MNT`	2010-11-23	Not announced
46.42.44.0/22	RIPE	OJSC Kostroma Municipal Telephone Network adsl users segment	`KMTN2-MNT`	2010-08-12	Not announced
46.42.48.0/22	RIPE	OAO KGTS adsl users segment	`KMTN2-MNT`	2010-11-23	Not announced
46.42.52.0/22	RIPE	OJSC Kostroma Municipal Telephone Network adsl users segment	`KMTN2-MNT`	2010-08-12	Not announced
46.42.56.0/22	RIPE	OAO KGTS adsl users segment	`KMTN2-MNT`	2010-11-23	Not announced
46.42.60.0/22	RIPE	OJSC Kostroma Municipal Telephone Network adsl users segment	`KMTN2-MNT`	2010-08-12	Not announced
188.120.48.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2013-01-28	Not announced
188.120.56.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2013-01-28	Not announced
5.175.88.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2012-08-03	Announced
46.42.0.0/18	RIPE	OAO KGTS	`KMTN2-MNT`	2010-11-18	Announced
46.42.16.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2010-11-18	Announced
46.42.24.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2010-11-18	Announced
46.42.32.0/21	RIPE	OAO KGTS adsl users segment	`KMTN2-MNT`	2010-11-23	Announced
46.42.40.0/21	RIPE	OAO KGTS adsl users segment	`KMTN2-MNT`	2010-11-23	Announced
46.42.48.0/21	RIPE	OAO KGTS adsl users segment	`KMTN2-MNT`	2010-11-23	Announced
46.42.56.0/21	RIPE	OAO KGTS adsl users segment	`KMTN2-MNT`	2010-11-18	Announced
46.228.96.0/20	RADB	Proxy-registered route object	`MAINT-AS3491`	2025-03-28	Announced
46.228.96.0/20	RIPE	OAO KGTS	`KMTN2-MNT`	2011-02-24	Announced
134.90.152.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2011-11-08	Announced
146.247.32.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2011-10-06	Announced
178.57.32.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2015-02-01	Announced
178.57.40.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2015-02-01	Announced
178.57.48.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2015-02-01	Announced
185.16.56.0/22	RIPE	OAO KGTS	`KMTN2-MNT`	2013-01-21	Announced
188.120.48.0/20	RIPE	OAO KGTS	`KMTN2-MNT`	2013-01-28	Announced
194.58.160.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2013-12-04	Announced
194.58.176.0/21	RIPE	OAO KGTS	`KMTN2-MNT`	2013-12-04	Announced

IRR

AS-sets

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

AS-set	Where	Relationship
`AS-ATEL-PEER`	RIPE	Lists AS44507 as a direct member
`AS-BLOCK-SET`	RIPE	Lists AS44507 as a direct member
`AS-BLOCKED-RU`	RIPE	Lists AS44507 as a direct member
`AS-ROSTELECOM`	RIPE	Lists AS44507 as a direct member
`AS-SET-IPV6-KMTN`	RIPE	Lists AS44507 as a direct member
`AS-SET-IPV6-SVEN`	RIPE	Lists AS44507 as a direct member
`AS-SET-KMTN`	RIPE	Lists AS44507 as a direct member
`AS-SET-SVEN`	RIPE	Lists AS44507 as a direct member
`AS-YARTELECOM`	RIPE	Lists AS44507 as a direct member
`AS209141:AS-RUCUST`	RADB	Lists AS44507 as a direct member
`AS3491:AS-CUSTOMERS-EU`	RADB	Lists AS44507 as a direct member
`AS41194:AS-RASCOM`	RIPE	Lists AS44507 as a direct member

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