Routing security

AS35810 BIGTELECOM-AS

Residential RIPE Cable/DSL/ISP

RPKI valid 0% 0 of 28 announcements

RPKI invalid 0 none

No ROA 28 not covered by any ROA

IRR registered 100% 0 missing · 0 other origin

ROAs 3 authorising this AS

Announcements

What this network originates

28 observed

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

Prefix	RPKI	IRR	Vantage points
2a00:1468::/48	No ROA	IRR	34
2a00:1468:8000::/34	No ROA	IRR	34
37.233.116.0/24	No ROA	IRR	53
37.233.117.0/24	No ROA	IRR	53
37.233.118.0/24	No ROA	IRR	53
37.233.119.0/24	No ROA	IRR	53
87.255.0.0/23	No ROA	IRR	53
87.255.2.0/23	No ROA	IRR	53
87.255.2.0/24	No ROA	IRR	53
87.255.3.0/24	No ROA	IRR	53
87.255.4.0/22	No ROA	IRR	53
87.255.8.0/22	No ROA	IRR	53
87.255.8.0/24	No ROA	IRR	53
87.255.9.0/24	No ROA	IRR	53
87.255.12.0/22	No ROA	IRR	53
87.255.16.0/21	No ROA	IRR	53
87.255.16.0/24	No ROA	IRR	53
87.255.17.0/24	No ROA	IRR	53
87.255.18.0/23	No ROA	IRR	53
87.255.20.0/22	No ROA	IRR	53
87.255.24.0/21	No ROA	IRR	53
185.233.192.0/22	No ROA	IRR	53
185.233.192.0/24	No ROA	IRR	53
185.233.193.0/24	No ROA	IRR	53
185.233.194.0/24	No ROA	IRR	53
185.233.195.0/24	No ROA	IRR	53
195.191.238.0/23	No ROA	IRR	53
195.191.238.0/24	No ROA	IRR	53

RPKI · ROAs

Route origin authorisations

3 ROAs

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

Prefix	Max length	Trust anchor
2a11:ec0::/32	/32	RIPENCC
2a14:a085::/32	/32	RIPENCC
2a14:a086::/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

36 objects · 8 not announced

Route objects naming AS35810 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
87.255.6.0/24	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2014-07-04	Not announced
87.255.10.0/23	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2008-02-12	Not announced
87.255.14.0/24	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2015-12-23	Not announced
195.191.239.0/24	RIPE	—	`BIGTELECOM-MNT`	2025-07-15	Not announced
2a05:c600::/29	RIPE	—	`LIR-RU-KOMSKOVIP-1-MNT`	2026-06-02	Not announced
2a11:ec0::/32	RIPE	—	`IP-RIPE`	2026-04-15	Not announced
2a14:a085::/32	RIPE	—	`LOCALNCC-MNT`	2026-03-25	Not announced
2a14:a086::/32	RIPE	—	`LOCALNCC-MNT`	2026-03-23	Not announced
37.233.116.0/24	RIPE	OOO Secret-Svyaz	`BIGTELECOM-MNT`	2025-02-27	Announced
37.233.117.0/24	RIPE	OOO Secret-Svyaz	`BIGTELECOM-MNT`	2025-02-27	Announced
37.233.118.0/24	RIPE	BIG TELECOM JSC	`BIGTELECOM-MNT`	2019-03-12	Announced
37.233.119.0/24	RIPE	OOO Secret-Svyaz	`BIGTELECOM-MNT`	2020-08-20	Announced
87.255.0.0/23	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2006-04-05	Announced
87.255.2.0/23	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2006-04-25	Announced
87.255.2.0/24	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2006-10-24	Announced
87.255.3.0/24	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2006-10-26	Announced
87.255.4.0/22	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2006-05-07	Announced
87.255.8.0/22	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2006-10-06	Announced
87.255.8.0/24	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2006-10-24	Announced
87.255.9.0/24	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2006-10-24	Announced
87.255.12.0/22	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2008-08-06	Announced
87.255.16.0/21	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2009-05-29	Announced
87.255.16.0/24	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2025-07-11	Announced
87.255.17.0/24	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2025-07-11	Announced
87.255.18.0/23	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2025-07-11	Announced
87.255.20.0/22	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2025-07-11	Announced
87.255.24.0/21	RIPE	BIG TELECOM CLOSED JSC	`BIGTELECOM-MNT`	2009-12-14	Announced
185.233.192.0/22	RIPE	—	`BIGTELECOM-MNT`	2017-12-07	Announced
185.233.192.0/24	RIPE	—	`BIGTELECOM-MNT`	2025-07-14	Announced
185.233.193.0/24	RIPE	—	`BIGTELECOM-MNT`	2025-07-14	Announced
185.233.194.0/24	RIPE	—	`BIGTELECOM-MNT`	2025-07-14	Announced
185.233.195.0/24	RIPE	—	`BIGTELECOM-MNT`	2025-07-14	Announced
195.191.238.0/23	RIPE	—	`BIGTELECOM-MNT`	2019-10-18	Announced
195.191.238.0/24	RIPE	—	`BIGTELECOM-MNT`	2025-07-15	Announced
2a00:1468::/48	RIPE	BIG Telecom IPV6 network	`BIGTELECOM-MNT`	2011-04-11	Announced
2a00:1468:8000::/34	RIPE	BIG Telecom Client IPV6 network	`BIGTELECOM-MNT`	2023-08-22	Announced

IRR

AS-sets

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

AS-set	Where	Relationship
`AS-BIGTELECOM`	PeeringDB	Declared by the operator as its own set
`AS-BIGTELECOM-IPV6`	PeeringDB	Declared by the operator as its own set
`AS-ASTEIS`	RIPE	Lists AS35810 as a direct member
`AS-BIGTELECOM`	RIPE	Lists AS35810 as a direct member
`AS-BIGTELECOM-IPV6`	RIPE	Lists AS35810 as a direct member
`AS-BLOCK-SET`	RIPE	Lists AS35810 as a direct member
`AS-BLOCKED-RU`	RIPE	Lists AS35810 as a direct member
`AS-HURRICANEV6`	RADB	Lists AS35810 as a direct member
`AS-RETN-ACTUAL-V4`	RIPE	Lists AS35810 as a direct member
`AS-RETN-ACTUAL-V6`	RIPE	Lists AS35810 as a direct member
`AS-TRANSROUTE-SPEC`	RIPE	Lists AS35810 as a direct member
`AS34251:AS-RUFILE`	RIPE	Lists AS35810 as a direct member
`AS3491:AS-CUSTOMERS-EU`	RADB	Lists AS35810 as a direct member
`AS41194:AS-RASCOM`	RIPE	Lists AS35810 as a direct member

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