Skip to main content

AS34123

NETORN-AS

Moscow, Russia

Registry

Authoritative registration data

AS number
34123
Name
NETORN-AS
Organisation
Moscow, Russia
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

11

IPv6 prefixes

1

Total announced

12

Announced prefixes

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

Prefixes announced by AS34123
188.35.0.0/16 IPv4 /16 not checked
89.222.128.0/17 IPv4 /17 not checked
178.219.144.0/21 IPv4 /21 not checked
89.222.248.0/21 IPv4 /21 not checked
185.94.172.0/22 IPv4 /22 not checked
188.35.152.0/22 IPv4 /22 not checked
188.35.168.0/22 IPv4 /22 not checked
188.35.184.0/22 IPv4 /22 not checked
89.222.206.0/23 IPv4 /23 not checked
188.35.40.0/24 IPv4 /24 not checked
89.222.192.0/24 IPv4 /24 not checked
2a00:12a0::/32 IPv6 /32 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

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

Source:ripestat:asn-neighbours observed

Observed upstreams

23 networks seen before AS34123 in AS paths

Observed upstreams
Families
AS50509 1,829 4,497
v4 v6
AS8641 1,223 3,677
v4 v6
AS6939 1,141 1,650
v4 v6
AS35598 434 1,124
v4 v6
AS8218 29 440
v4 v6
AS25091 68 390
v4 v6
AS47692 23 154
v4 v6
AS50673 37 108
v4
AS49434 25 87
v4 v6
AS9198 17 59
v4 v6
AS15958 16 54
v4
AS137409 13 52
v4
AS41327 17 49
v4 v6
AS6663 13 42
v4
AS60171 11 39
v4 v6
AS42295 11 35
v4
AS14840 4 25
v4
AS56911 7 20
v4
AS62000 2 5
v4
AS263444 2 5
v4
AS56655 3 4
v4 v6
AS43727 1 2
v4
AS207351 1 1
v4

No rows match “”.

Showing of

Observed downstreams

18 networks seen after AS34123 in AS paths

Observed downstreams
Families
AS42148 572 1,658
v4 v6
AS50553 580 1,497
v4
AS58036 532 1,140
v4 v6
AS51579 464 1,082
v4 v6
AS34139 367 1,004
v4 v6
AS50668 293 624
v4
AS48149 283 575
v4
AS8395 334 472
v4 v6
AS57368 291 386
v4
AS59793 258 367
v6
AS209558 200 260
v4
AS49583 45 171
v4
AS41842 92 123
v4
AS57456 30 100
v4
AS47711 55 75
v4
AS28738 4 42
v4
AS43865 3 18
v4
AS47286 3 3
v4

No rows match “”.

Showing of

Uncertain adjacencies

20 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 16 282
v4 v6
AS36236 27 84
v4 v6
AS49673 22 67
v4
AS3170 20 64
v4 v6
AS29049 18 61
v4
AS205112 14 50
v4 v6
AS208972 17 48
v4 v6
AS200612 18 47
v4
AS51185 12 47
v4
AS199524 14 45
v4
AS13004 14 42
v4
AS41722 17 40
v4 v6
AS209823 12 40
v4 v6
AS44901 14 39
v4
AS37721 11 35
v4
AS28917 7 30
v4 v6
AS28910 4 10
v4 v6
AS212483 2 10
v4
AS20764 1 2
v4
AS39351 1 1
v4

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.