Skip to main content

AS44141

DEVCLIC-AS

------------------------------------------------

Registry

Authoritative registration data

AS number
44141
Name
DEVCLIC-AS
Organisation
------------------------------------------------
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 AS44141
46.31.40.0/21 IPv4 /21 not checked
185.13.64.0/22 IPv4 /22 not checked
185.67.74.0/23 IPv4 /23 not checked
91.198.44.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 AS44141
Address families
AMS-IX 100 Mbps IPv4 · IPv6
Equinix Paris: Equinix IX - PA Metro 1,000 Mbps IPv4
France-IX Paris 10,000 Mbps IPv4
Hopus 10,000 Mbps IPv4
LU-CIX 100 Mbps IPv4 · IPv6
TOP-IX: Public Peering VLAN 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 AS44141 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

35 networks seen before AS44141 in AS paths

No rows match “”.

Showing of

Observed downstreams

2 networks seen after AS44141 in AS paths

Observed downstreams
Families
AS196658 132 491
v4
AS197551 142 187
v4

No rows match “”.

Showing of

Uncertain adjacencies

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