Skip to main content

AS29588

IVSTARNET-AS

--Uplinks--

Registry

Authoritative registration data

AS number
29588
Name
IVSTARNET-AS
Organisation
--Uplinks--
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

2

Total announced

14

Announced prefixes

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

Prefixes announced by AS29588
213.108.136.0/21 IPv4 /21 not checked
91.247.248.0/22 IPv4 /22 not checked
213.108.136.0/24 IPv4 /24 not checked
213.108.137.0/24 IPv4 /24 not checked
213.108.138.0/24 IPv4 /24 not checked
213.108.140.0/24 IPv4 /24 not checked
213.108.142.0/24 IPv4 /24 not checked
213.108.143.0/24 IPv4 /24 not checked
91.247.248.0/24 IPv4 /24 not checked
91.247.249.0/24 IPv4 /24 not checked
91.247.250.0/24 IPv4 /24 not checked
91.247.251.0/24 IPv4 /24 not checked
2a0e:e6c0:6000::/36 IPv6 /36 not checked
2a00:f440:a::/48 IPv6 /48 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 AS29588
Address families
CLOUD-IX MSK 10,000 Mbps IPv4 · IPv6
GNM-IX 10,000 Mbps IPv4 · IPv6
PITER-IX Helsinki 10,000 Mbps IPv4
PITER-IX Kiev 10,000 Mbps IPv4
PITER-IX Moscow: MSK_PEERING_VLAN 10,000 Mbps IPv4 · IPv6
PITER-IX Riga: RIX_PEERING_VLAN 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 AS29588 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

21 networks seen before AS29588 in AS paths

Observed upstreams
Families
AS35598 102 1,507
v4 v6
AS9002 RETN-AS 105 959
v4 v6
AS20764 RASCOM-AS 74 828
v4 v6
AS31500 48 648
v4 v6
AS29076 121 565
v4 v6
AS6939 HURRICANE 123 169
v6
AS8218 NEO-ASN 3 100
v4 v6
AS25091 IP-Max 3 78
v4 v6
AS202984 team-host 7 70
v4
AS47692 2 52
v4 v6
AS1299 TWELVE99 25 49
v6
AS48347 8 44
v4 v6
AS60171 1 14
v4 v6
AS6663 1 13
v4 v6
AS9198 1 13
v4 v6
AS6204 1 12
v4
AS15958 1 12
v4
AS42295 TBISS-AS 1 12
v4
AS137409 GSLNETWORKS-AS-AP 1 12
v4
AS62255 BEMYLINK 1 10
v4
AS56655 GIGAHOST 1 1
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS29588 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

18 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 66
v4 v6
AS3170 1 14
v4 v6
AS41327 FIBERTELECOM-AS 1 14
v4 v6
AS49434 1 14
v4 v6
AS57304 1 14
v4 v6
AS205112 PHILUNET 1 14
v4 v6
AS209823 1 14
v4 v6
AS41722 1 13
v4 v6
AS199524 GCORE 1 13
v4 v6
AS13004 1 12
v4
AS37721 ORG-VTS1-AFRINIC 1 12
v4
AS44901 1 12
v4
AS49673 TRUENETWORK 1 12
v4
AS51185 MAINSTREAMING-AS 1 12
v4
AS200612 GulfBridgeInternational 1 12
v4
AS208972 1 12
v4
AS28910 1 2
v6
AS39351 ESAB-AS 1 1
v6

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.