Network · data from 2026-11-12

AS33842 Cross Tel

Registry name: NOT_USED Citytelecom LLC, RU · PeeringDB

23IPv4 routes 100.0% RPKI valid · 95.7% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS33842, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS33842, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


201.8.90.0/24	Valid	None	673 100%	66
31.77.71.0/24	Valid	RIR databaseRIPE	673 100%	66
37.235.241.0/24	Valid	RIR databaseRIPE	673 100%	66
78.17.98.0/24	Valid	RIR databaseRIPE	673 100%	66
78.17.181.0/24	Valid	RIR databaseRIPE	673 100%	66
80.71.224.0/24	Valid	RIR databaseRIPE	673 100%	66
89.125.121.0/24	Valid	RIR databaseRIPE	673 100%	66
89.125.214.0/24	Valid	RIR databaseRIPE	673 100%	66
95.181.212.0/23	Valid	RIR databaseRIPE	673 100%	66
104.143.201.0/24	Valid	RIR databaseRIPE	673 100%	66
109.61.108.0/24	Valid	RIR databaseRIPE	673 100%	66
132.243.195.0/24	Valid	RIR databaseRIPE	673 100%	66
132.243.214.0/24	Valid	RIR databaseRIPE	673 100%	66
132.243.230.0/24	Valid	RIR databaseRIPE	673 100%	66
144.31.48.0/24	Valid	RIR databaseRIPE	673 100%	66
144.31.61.0/24	Valid	RIR databaseRIPE	673 100%	66
147.45.219.0/24	Valid	RIR databaseRIPE	673 100%	66
185.73.126.0/24	Valid	RIR databaseRIPE	673 100%	66
185.182.65.0/24	Valid	RIR databaseRIPE	673 100%	66
195.170.163.0/24	Valid	RIR databaseRIPE	673 100%	66
212.119.42.0/24	Valid	RIR databaseRIPE	673 100%	67
179.253.173.0/24	Valid	RIR databaseRIPE	672 100%	66
191.223.140.0/24	Valid	RIR databaseRIPE	672 100%	66

AS-SET

PeeringDB's irr_as_set for AS33842: AS-RU-CROSSTEL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS33842 isn't in the set, or no route object for AS33842 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS33842 in it	Not covered
AS-RU-CROSSTEL	In no IRR database read today.

Name

Database

ASNs

Sets

Route objects

AS33842 in it

Not covered

AS-RU-CROSSTEL

In no IRR database read today.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.

Route object: none1
AS-SET: not found1

Change	Prefix or set	Detail	Full-table peers
Route object: none	201.8.90.0/24	No route object for it. Add a route object with origin AS33842 in the RIR database for the space.	673 of 673
AS-SET: not found	AS-RU-CROSSTEL	PeeringDB names AS-RU-CROSSTEL; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: none

201.8.90.0/24

No route object for it. Add a route object with origin AS33842 in the RIR database for the space.

673 of 673

AS-SET: not found

AS-RU-CROSSTEL

PeeringDB names AS-RU-CROSSTEL; no IRR database read has it.

Route objects not announced

Every route object with origin AS33842 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.