Skip to main content

AS60072

EGS-Telecom-AS

LLC EGS-Telecom

Registry

Authoritative registration data

AS number
60072
Name
EGS-Telecom-AS
Organisation
LLC EGS-Telecom
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS60072
31.171.192.0/21 IPv4 /21 not checked
185.58.216.0/22 IPv4 /22 not checked
185.58.219.0/24 IPv4 /24 not checked
31.171.198.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 AS60072 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS60072 in AS paths

Observed upstreams
Families
AS60764 TK-Telecom 301 958
v4
AS20485 80 321
v4
AS31133 53 208
v4
AS25091 IP-Max 2 8
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS60072 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 6
v4
AS29049 1 2
v4
AS36236 NETACTUATE 1 2
v4
AS41327 FIBERTELECOM-AS 1 2
v4
AS41722 1 2
v4
AS49673 TRUENETWORK 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.