Skip to main content

AS204280

sielte

SIELTE S.P.A.

Registry

Authoritative registration data

AS number
204280
Name
sielte
Organisation
SIELTE S.P.A.
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS204280
185.107.184.0/22 IPv4 /22 not checked
185.107.187.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 AS204280
Address families
MIX Palermo 10,000 Mbps IPv4 · IPv6
MIX-IT 10,000 Mbps IPv4 · IPv6
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 AS204280 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS204280 in AS paths

Observed upstreams
Families
AS34428 EIGHTROUTE 251 484
v4
AS47408 MANDARIN-AS 111 143
v4
AS6939 HURRICANE 22 23
v4
AS3269 ASN-IBSNAZ 13 23
v4
AS8218 NEO-ASN 3 10
v4
AS5405 INTERDOTLINK 3 4
v4
AS4455 BSO 2 3
v4
AS6204 ZET-NET 1 1
v4
AS31543 MYNET-AS 1 1
v4
AS60171 AFRIX-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

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