Skip to main content

AS31059

AVELACOM-AS

==================

Registry

Authoritative registration data

AS number
31059
Name
AVELACOM-AS
Organisation
==================
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

0

Total announced

0

Announced prefixes

No announced prefixes observed

Route collectors saw no announcements from this AS, or the routing data source was unavailable.

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS31059
Address families
DE-CIX Frankfurt: DE-CIX Frankfurt Peering LAN 1,000 Mbps IPv4 · IPv6
LINX LON1: Main 2,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 AS31059 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS31059 in AS paths

Observed upstreams
Families
AS41095 170 416
v4
AS174 COGENT-174 188 388
v4
AS3223 VOXILITY 139 314
v4
AS4657 STARHUB-INTERNET 55 167
v4
AS3257 GTT-BACKBONE 104 163
v4
AS1299 TWELVE99 99 117
v4
AS10099 UNICOM-Global 46 106
v4
AS6939 HURRICANE 20 21
v4
AS1836 GREEN 2 7
v4
AS140951 3 6
v4
AS286 1 1
v4

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS31059 in AS paths

Observed downstreams
Families
AS208783 807 1,683
v4
AS215182 24 27
v4

No rows match “”.

Showing of

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS18106 VIEWQWEST-SG-AP 1 1
v4
AS48237 MOBILY-AS 1 1
v4
AS207841 INFERNO 1 1
v4
AS271253 1 1
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.