Skip to main content

AS39513

ONECOM-AS

=== IXP ===

Registry

Authoritative registration data

AS number
39513
Name
ONECOM-AS
Organisation
=== IXP ===
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS39513
193.93.76.0/22 IPv4 /22 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 AS39513
Address families
1-BG FREE 10,000 Mbps IPv4 · IPv6
1-CZ FREE 10,000 Mbps IPv4 · IPv6
1-DE FREE 10,000 Mbps IPv4 · IPv6
1-ES FREE 10,000 Mbps IPv4 · IPv6
1-FR FREE 10,000 Mbps IPv4 · IPv6
1-IX EU 20,000 Mbps IPv4 · IPv6
1-IX UA 20,000 Mbps IPv4 · IPv6
1-PL FREE 10,000 Mbps IPv4 · IPv6
1-SK FREE 100,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 AS39513 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS39513 in AS paths

Observed upstreams
Families
AS3257 GTT-BACKBONE 144 174
v4
AS50263 112 137
v4
AS6939 HURRICANE 19 20
v4
AS8218 NEO-ASN 5 17
v4
AS60159 EUROLINE-NET 8 11
v4
AS14840 ASN14840 2 5
v4
AS49434 FBWNETWORKS 3 3
v4
AS6204 2 2
v4
AS62000 1 1
v4
AS264409 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS39513 in AS paths

Observed downstreams
Families
AS45022 20 29
v4
AS43998 TRINITY-KYIV 11 13
v4

No rows match “”.

Showing – of

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 9
v4
AS34927 iFog-GmbH 1 2
v4
AS212483 level86 1 2
v4
AS50629 LWLCOM 1 1
v4
AS198150 SIACOM-AS 1 1
v4
AS209823 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.