Skip to main content

AS31655

ASN-GammaTelecom

Gamma Telecom Holdings Ltd

Registry

Authoritative registration data

AS number
31655
Name
ASN-GammaTelecom
Organisation
Gamma Telecom Holdings Ltd
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

36

IPv6 prefixes

3

Total announced

39

Announced prefixes

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

Prefixes announced by AS31655
157.125.0.0/16 IPv4 /16 not checked
157.231.0.0/16 IPv4 /16 not checked
51.219.0.0/16 IPv4 /16 not checked
51.52.0.0/16 IPv4 /16 not checked
79.74.0.0/16 IPv4 /16 not checked
92.207.0.0/16 IPv4 /16 not checked
138.248.128.0/17 IPv4 /17 not checked
151.2.128.0/17 IPv4 /17 not checked
164.39.128.0/17 IPv4 /17 not checked
62.223.128.0/17 IPv4 /17 not checked
188.66.64.0/18 IPv4 /18 not checked
88.215.0.0/18 IPv4 /18 not checked
195.162.96.0/19 IPv4 /19 not checked
5.2.96.0/19 IPv4 /19 not checked
138.248.16.0/20 IPv4 /20 not checked
138.248.32.0/20 IPv4 /20 not checked
193.39.16.0/20 IPv4 /20 not checked
213.218.192.0/20 IPv4 /20 not checked
80.252.64.0/20 IPv4 /20 not checked
89.213.16.0/20 IPv4 /20 not checked
46.227.48.0/21 IPv4 /21 not checked
89.213.32.0/21 IPv4 /21 not checked
89.213.8.0/21 IPv4 /21 not checked
151.2.128.0/22 IPv4 /22 not checked
151.2.132.0/22 IPv4 /22 not checked
151.2.136.0/22 IPv4 /22 not checked
151.2.140.0/22 IPv4 /22 not checked
185.21.208.0/22 IPv4 /22 not checked
185.4.196.0/22 IPv4 /22 not checked
185.47.104.0/22 IPv4 /22 not checked
185.9.232.0/22 IPv4 /22 not checked
5.144.156.0/22 IPv4 /22 not checked
138.248.140.0/24 IPv4 /24 not checked
185.157.103.0/24 IPv4 /24 not checked
51.52.50.0/24 IPv4 /24 not checked
62.223.251.0/24 IPv4 /24 not checked
2a02:c1c0::/29 IPv6 /29 not checked
2a02:df80::/29 IPv6 /29 not checked
2a04:4440::/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 AS31655
Address families
LINX LON1: Main 200,000 Mbps IPv4 · IPv6
LINX LON2 40,000 Mbps IPv4 · IPv6
LINX Manchester 40,000 Mbps IPv4 · IPv6
LONAP: LON0 200,000 Mbps IPv4 · IPv6

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 AS31655 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS31655 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 1,010 7,523
v4 v6
AS2914 NTT-DATA-2914 691 4,352
v4 v6
AS6939 HURRICANE 140 894
v4
AS13030 INIT7 61 497
v4 v6
AS33891 CORE-BACKBONE 46 278
v4 v6
AS35280 F5 39 250
v4 v6
AS8220 COLT 15 149
v4 v6
AS4455 14 126
v4
AS39351 ESAB-AS 16 96
v4 v6
AS8455 ATOM86-AS 13 91
v4 v6
AS4637 ASN-TELSTRA-GLOBAL 13 86
v4 v6
AS61049 9 52
v4 v6
AS9009 M247 7 42
v4
AS15802 DU-AS1 6 41
v4
AS8943 1 23
v4

No rows match “”.

Showing of

Observed downstreams

6 networks seen after AS31655 in AS paths

Observed downstreams
Families
AS204193 267 999
v4
AS8918 266 405
v4
AS198472 266 335
v4
AS216167 265 335
v4
AS41553 266 333
v4
AS205237 200 237
v4

No rows match “”.

Showing of

Uncertain adjacencies

15 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 7 486
v4 v6
AS51185 MAINSTREAMING-AS 7 92
v4 v6
AS49544 i3Dnet 7 90
v4 v6
AS25160 VORBOSS 7 89
v4 v6
AS3170 7 47
v4 v6
AS15692 RAZORBLUE 7 47
v4 v6
AS31742 SOTACONNECT 7 47
v4 v6
AS14630 INVESCO 7 45
v4 v6
AS35266 EXN-AS 7 45
v4 v6
AS36236 NETACTUATE 7 45
v4 v6
AS48070 7 45
v4 v6
AS50300 7 45
v4 v6
AS28792 7 42
v4
AS8426 CLARANET-AS 6 41
v4
AS18106 VIEWQWEST-SG-AP 6 41
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.