Skip to main content

AS39684

MANGO-TELECOM-AS

OOO Mango Telecom

Registry

Authoritative registration data

AS number
39684
Name
MANGO-TELECOM-AS
Organisation
OOO Mango Telecom
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

0

Total announced

12

Announced prefixes

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

Prefixes announced by AS39684
81.88.80.0/22 IPv4 /22 RPKI valid
185.200.140.0/24 IPv4 /24 RPKI valid
185.200.141.0/24 IPv4 /24 RPKI valid
185.200.142.0/24 IPv4 /24 not checked
81.88.84.0/24 IPv4 /24 not checked
81.88.85.0/24 IPv4 /24 not checked
81.88.86.0/24 IPv4 /24 not checked
81.88.87.0/24 IPv4 /24 RPKI valid
81.88.88.0/24 IPv4 /24 RPKI valid
81.88.89.0/24 IPv4 /24 not checked
81.88.94.0/24 IPv4 /24 RPKI valid
81.88.95.0/24 IPv4 /24 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 AS39684 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

18 networks seen before AS39684 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS39684 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 18
v4
AS35598 INETCOM 1 6
v4
AS36236 NETACTUATE 1 6
v4
AS41722 MIRAN-AS 1 6
v4
AS49673 TRUENETWORK 1 6
v4
AS28910 INTAL-ASN 1 2
v4
AS28917 Fiord-AS 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.