Skip to main content

AS36666

GTCOMM

GloboTech Communications

Registry

Authoritative registration data

AS number
36666
Name
GTCOMM
Organisation
GloboTech Communications
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

3

Total announced

17

Announced prefixes

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

Prefixes announced by AS36666
173.209.32.0/19 IPv4 /19 not checked
67.215.0.0/20 IPv4 /20 not checked
67.43.224.0/20 IPv4 /20 not checked
68.168.112.0/20 IPv4 /20 not checked
72.10.160.0/20 IPv4 /20 not checked
41.77.112.0/21 IPv4 /21 not checked
74.120.220.0/22 IPv4 /22 not checked
38.128.236.0/23 IPv4 /23 not checked
173.209.32.0/24 IPv4 /24 not checked
196.32.219.0/24 IPv4 /24 not checked
196.32.220.0/24 IPv4 /24 not checked
198.145.107.0/24 IPv4 /24 not checked
208.99.63.0/24 IPv4 /24 not checked
67.43.237.0/24 IPv4 /24 not checked
2001:19c0::/32 IPv6 /32 not checked
2c0f:ee40:3000::/36 IPv6 /36 not checked
2620:c1:6000::/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 AS36666
Address families
CANIX Montreal 20,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 AS36666 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS36666 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 730 5,823
v4 v6
AS6461 ZAYO-6461 130 1,429
v4 v6
AS396998 PATH-NETWORK 303 673
v4
AS174 COGENT-174 81 478
v4 v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS36666 in AS paths

Observed downstreams
Families
AS149440 EVOXTSDNBHD-AS-AP 333 1,510
v4 v6
AS402194 286 625
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 3 42
v4 v6
AS1403 3 26
v4 v6
AS22652 3 21
v4 v6
AS36236 NETACTUATE 3 21
v4 v6
AS35280 F5 2 15
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.