Skip to main content

AS39419

CISEL

Dina IT Solutions SA

Registry

Authoritative registration data

AS number
39419
Name
CISEL
Organisation
Dina IT Solutions SA
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 AS39419
185.237.24.0/22 IPv4 /22 RPKI valid
195.141.249.0/24 IPv4 /24 not checked
2a0c:180::/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 AS39419
Address families
SwissIX: Peering — 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 AS39419 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS39419 in AS paths

Observed upstreams
Families
AS25091 IP-Max 239 755
v4 v6
AS6939 HURRICANE 54 85
v4 v6
AS6730 SUNRISE 13 43
v4 v6
AS8218 NEO-ASN 2 23
v4 v6
AS48362 TKSWF-AS 2 12
v4 v6
AS34019 HIVANE 2 11
v4 v6
AS9002 RETN-AS 4 8
v6
AS39351 ESAB-AS 2 5
v4 v6
AS5405 INTERDOTLINK 2 4
v4 v6
AS1764 NEXTLAYER-AS 1 3
v4 v6
AS1836 GREEN 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS39419 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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