Skip to main content

AS213462

FibreConnect-AS

FibreConnect S.p.A.

Registry

Authoritative registration data

AS number
213462
Name
FibreConnect-AS
Organisation
FibreConnect S.p.A.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS213462
62.50.140.0/22 IPv4 /22 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 AS213462
Address families
MIX-IT 200,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 AS213462 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS213462 in AS paths

Observed upstreams
Families
AS9002 RETN-AS 115 139
v4
AS3257 GTT-BACKBONE 59 64
v4
AS6939 HURRICANE 17 18
v4
AS8218 NEO-ASN 4 9
v4
AS14840 ASN14840 2 5
v4
AS4455 BSO 2 3
v4
AS5405 INTERDOTLINK 2 2
v4
AS24961 MYLOC-AS 2 2
v4
AS29075 IELO 2 2
v4
AS58807 CMI-INT-AS 1 2
v4
AS286 KPN 1 1
v4
AS6204 ZET-NET 1 1
v4
AS9009 M247 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS213462 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.