Skip to main content

AS58082

AS-MESSAGENET

Messagenet S.p.A.

Registry

Authoritative registration data

AS number
58082
Name
AS-MESSAGENET
Organisation
Messagenet S.p.A.
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS58082
109.233.128.0/21 IPv4 /21 not checked
109.233.129.0/24 IPv4 /24 not checked
109.233.132.0/24 IPv4 /24 not checked
109.233.135.0/24 IPv4 /24 not checked
2a01:9300::/32 IPv6 /32 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 AS58082
Address families
MINAP Milan: MINAP 10,000 Mbps IPv4
MIX-IT 10,000 Mbps IPv4
Namex Rome: VLAN Peering 10,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 AS58082 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS58082 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 234 532
v4 v6
AS6762 SEABONE-NET 145 363
v4 v6
AS3356 LEVEL3 97 315
v4
AS41327 FIBERTELECOM-AS 68 265
v4
AS3257 GTT-BACKBONE 60 184
v4
AS12637 SEEWEB 2 6
v4
AS1267 2 4
v4
AS50877 AIRBEAM-AS 2 4
v4
AS286 KPN 1 3
v4
AS3269 ASN-IBSNAZ 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS58082 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS20811 BRENNERCOM-AS 1 3
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.