Skip to main content

AS211391

MITAN-AS

Mitan Telematica S.r.l.

Registry

Authoritative registration data

AS number
211391
Name
MITAN-AS
Organisation
Mitan Telematica S.r.l.
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 AS211391
109.236.168.0/21 IPv4 /21 not checked
150.251.64.0/21 IPv4 /21 not checked
194.105.36.0/22 IPv4 /22 not checked
193.3.57.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

Internet Exchange memberships listed for AS211391
Address families
MIX-IT 10,000 Mbps IPv4

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 AS211391 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS211391 in AS paths

Observed upstreams
Families
AS41327 FIBERTELECOM-AS 177 840
v4
AS6939 HURRICANE 19 80
v4
AS60475 XMATICA-AS 11 52
v4
AS8218 NEO-ASN 4 32
v4
AS14840 ASN14840 2 20
v4
AS5405 INTERDOTLINK 2 8
v4
AS24961 MYLOC-AS 2 8
v4
AS4455 BSO 1 4
v4
AS6204 ZET-NET 1 4
v4
AS60171 AFRIX-AS 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS211391 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

17 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.