Skip to main content

AS47626

ASTIMER

---Upstreams---

Registry

Authoritative registration data

AS number
47626
Name
ASTIMER
Organisation
---Upstreams---
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

16

IPv6 prefixes

1

Total announced

17

Announced prefixes

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

Prefixes announced by AS47626
176.118.224.0/19 IPv4 /19 not checked
5.59.128.0/19 IPv4 /19 not checked
188.93.64.0/22 IPv4 /22 not checked
193.35.48.0/22 IPv4 /22 not checked
193.7.216.0/22 IPv4 /22 not checked
5.180.240.0/22 IPv4 /22 not checked
78.24.100.0/22 IPv4 /22 not checked
128.0.86.0/23 IPv4 /23 not checked
91.205.190.0/23 IPv4 /23 not checked
128.0.92.0/24 IPv4 /24 not checked
128.0.94.0/24 IPv4 /24 not checked
176.96.189.0/24 IPv4 /24 not checked
213.241.199.0/24 IPv4 /24 not checked
91.208.35.0/24 IPv4 /24 not checked
91.222.120.0/24 IPv4 /24 not checked
91.222.121.0/24 IPv4 /24 not checked
2a05:9c00::/29 IPv6 /29 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 AS47626
Address families
Eurasia Peering IX: Peering LAN 10,000 Mbps IPv4
GNM-IX 60,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 20,000 Mbps IPv4
MSK-IX Rostov-on-Don 10,000 Mbps IPv4
PITER-IX Frankfurt 40,000 Mbps IPv4
PITER-IX Helsinki 40,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 40,000 Mbps IPv4
PITER-IX Riga: RIX_PEERING_VLAN 40,000 Mbps IPv4
PITER-IX Saint-Petersburg: SPB_PEERING_VLAN 40,000 Mbps IPv4
PITER-IX Tallinn: TLL_PEERING VLAN 40,000 Mbps IPv4
Sea-IX 30,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 AS47626 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

26 networks seen before AS47626 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 757 3,792
v4 v6
AS31500 518 3,035
v4
AS31133 695 2,486
v4 v6
AS28917 189 896
v4
AS8218 NEO-ASN 17 368
v4
AS6939 HURRICANE 89 356
v4
AS25091 IP-Max 33 207
v4
AS47692 24 198
v4
AS57304 57 105
v4 v6
AS49434 20 96
v4
AS61049 19 71
v4
AS15958 14 57
v4
AS6204 10 51
v4
AS60171 11 49
v4
AS41327 FIBERTELECOM-AS 13 48
v4
AS137409 GSLNETWORKS-AS-AP 8 48
v4
AS42295 TBISS-AS 8 43
v4
AS6663 6 40
v4
AS9198 12 39
v4
AS39351 ESAB-AS 7 29
v4
AS34927 iFog-GmbH 5 27
v4
AS56655 GIGAHOST 5 20
v4
AS50673 6 16
v4
AS62000 1 16
v4
AS8447 2 2
v4
AS43727 2 2
v4

No rows match “”.

Showing of

Observed downstreams

25 networks seen after AS47626 in AS paths

Observed downstreams
Families
AS45055 142 3,540
v4
AS197185 400 583
v4 v6
AS208720 246 450
v4
AS57766 291 369
v4
AS58306 277 352
v4
AS209393 112 298
v4
AS57531 110 268
v4
AS58096 31 225
v4
AS56374 173 219
v4
AS199008 20 168
v4
AS59416 105 123
v4
AS42922 40 116
v4
AS57534 19 114
v4
AS24758 18 72
v4
AS203695 19 56
v4
AS49897 45 53
v4
AS47709 36 42
v4
AS60936 7 36
v4
AS57396 26 32
v4
AS208544 14 32
v4
AS209219 16 16
v4
AS41743 2 12
v4
AS206649 5 5
v4
AS47551 2 2
v4
AS57990 2 2
v4

No rows match “”.

Showing of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 14 287
v4
AS35598 26 73
v4
AS208972 16 59
v4
AS13004 15 58
v4
AS44901 13 56
v4
AS200612 GulfBridgeInternational 14 54
v4
AS3170 13 54
v4
AS205112 PHILUNET 12 52
v4
AS37721 ORG-VTS1-AFRINIC 11 51
v4
AS209823 9 45
v4
AS41722 14 43
v4
AS29049 13 42
v4
AS51185 MAINSTREAMING-AS 7 41
v4
AS36236 NETACTUATE 11 40
v4
AS49673 TRUENETWORK 5 23
v4
AS28910 4 20
v4
AS199524 GCORE 1 7
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.