Skip to main content

AS57913

toscanatlc

--------------------------------------------

Registry

Authoritative registration data

AS number
57913
Name
toscanatlc
Organisation
--------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS57913
37.61.228.0/24 IPv4 /24 not checked
81.30.109.0/24 IPv4 /24 not checked
2a13:f600::/29 IPv6 /29 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 AS57913
Address families
MINAP Milan: MINAP 1,000 Mbps IPv4 · IPv6
MIX-IT 2,000 Mbps IPv4 · IPv6
Namex Rome: VLAN Peering 1,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 AS57913 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS57913 in AS paths

Observed upstreams
Families
AS41327 FIBERTELECOM-AS 175 514
v4 v6
AS6939 HURRICANE 69 118
v4 v6
AS5398 InternetONE 38 86
v4 v6
AS8218 NEO-ASN 5 24
v4 v6
AS14840 ASN14840 2 15
v4 v6
AS24482 SGGS-AS-AP 2 10
v4 v6
AS5405 INTERDOTLINK 3 6
v4 v6
AS24961 MYLOC-AS 2 6
v4 v6
AS29632 NASSIST-AS 3 3
v6
AS4455 BSO 1 3
v4 v6
AS6204 ZET-NET 1 2
v4
AS60171 AFRIX-AS 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS57913 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

18 adjacencies that may be an artefact of collector peering

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.