Skip to main content

AS35026

GELICON-AS

Gelicon-Apple Limited liability company

Registry

Authoritative registration data

AS number
35026
Name
GELICON-AS
Organisation
Gelicon-Apple Limited liability company
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

2

Total announced

7

Announced prefixes

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

Prefixes announced by AS35026
37.139.84.0/22 IPv4 /22 not checked
37.139.84.0/23 IPv4 /23 not checked
37.139.84.0/24 IPv4 /24 not checked
37.139.85.0/24 IPv4 /24 not checked
37.139.86.0/24 IPv4 /24 not checked
2a03:cf40::/32 IPv6 /32 not checked
2a03:cf40::/40 IPv6 /40 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS35026 in AS paths

Observed upstreams
Families
AS35598 706 1,497
v4 v6
AS62255 BEMYLINK 62 167
v4 v6
AS25091 IP-Max 9 51
v4
AS24482 SGGS-AS-AP 2 46
v4
AS137409 GSLNETWORKS-AS-AP 4 13
v4
AS34927 iFog-GmbH 2 9
v4
AS49434 2 8
v4
AS61049 2 6
v4
AS9198 1 5
v4
AS8732 COMCOR-AS 1 3
v4
AS13194 BITE 1 3
v4
AS202984 team-host 1 3
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS35026 in AS paths

Observed downstreams
Families
AS198675 1 1
v4

No rows match “”.

Showing of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS37721 ORG-VTS1-AFRINIC 2 6
v4
AS49544 i3Dnet 1 4
v4
AS28910 1 3
v4
AS41327 FIBERTELECOM-AS 1 2
v4
AS199524 GCORE 1 2
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.