Skip to main content

AS51904

UTEX-AS

====UPLINKS====

Registry

Authoritative registration data

AS number
51904
Name
UTEX-AS
Organisation
====UPLINKS====
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS51904
193.41.76.0/22 IPv4 /22 not checked
91.132.104.0/22 IPv4 /22 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS51904
Address families
MSK-IX Moscow: MSK-IX peering network 10,000 Mbps IPv4 · IPv6
PITER-IX Frankfurt 10,000 Mbps IPv4
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Riga: RIX_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Rostov 10,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 10,000 Mbps IPv4
PITER-IX Tallinn: TLL_PEERING VLAN 10,000 Mbps IPv4

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS51904 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS51904 in AS paths

Observed upstreams
Families
AS8641 NAUKANET-AS 286 467
v4
AS57304 RETNRU-AS 213 353
v4
AS35598 INETCOM 202 313
v4
AS62255 BEMYLINK 39 65
v4
AS25091 IP-Max 8 20
v4
AS9198 KAZTELECOM-AS 2 3
v4
AS9002 RETN-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS51904 in AS paths

Observed downstreams
Families
AS51538 tekcom 255 304
v4
AS57724 DDOS-GUARD 131 169
v4
AS35598 INETCOM 105 125
v4
AS8641 NAUKANET-AS 20 48
v4
AS199624 DKTEL-AS 2 4
v4

No rows match “”.

Showing – of

Uncertain adjacencies

8 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.