Stats

Counting began on May 10, 2018. From our download metrics and considering out-of-band channels for obtaining Caddy, it seems that this telemetry data represents only about 1% of the true population of Caddy instances.
-
requests served
-
connections secured
-
certificates managed
-
instances started
-
running now
Caddy Telemetry
-
dev instances
-
production instances
Look up your Caddy:

FAQ

What is this?

You're looking at near-real-time metrics reported by Caddy from around the globe. This data comes from the Caddy Telemetry Project, which is a collective effort undertaken in 2018 to observe the health of the Internet from a server-side perspective. You can look up your own Caddy instances on this page to gain insights as to their usage and behavior, and you can enjoy the benefits of using it as a sort of free monitoring tool when you want to check in on things.

What are the benefits?

Site owners can use this resource to easily check on their server processes and observe trends over time or analyze the data for anomalies. Because this is data set is not constrained to one particular network or proprietary source, the research community now has access to a global, server-side perspective of the Internet for the first time. Our vision is high: hopefully, as this project advances, we may be able to monitor the health of the Web and detect emerging attacks or changes as they happen in real-time. Additionally, information provided by Caddy telemetry may be useful when designing new Web standards, network infrastructure, and Internet software.

Where can I read more about telemetry?

The specifics of how this works and the metrics that are reported can be found on the Telemetry documentation page.

How do I find my instance ID?

A universally unique ID (UUID) is randomly generated when you run Caddy if one is not already in the ~/.caddy or $CADDYPATH folder. You can get your instance ID from the file called uuid in that folder. In general, the command cat ~/.caddy/uuid works nicely.

Does each Caddy instance have its own UUID?

Most of the time, yes. Each Caddy instance should have its own $CADDYPATH (a folder to store things in). By default, that path is $HOME/.caddy. If multiple Caddy instances share this path, they will share the same UUID, which may not be desirable if you want to differentiate them.

How do I get access to all of the data?

At this time, we're happy to make the full data set freely available to researchers with well-defined research objectives. Please write to matt@lightcodelabs.com with your name, the institution you're associated with, and describe your interest in the data. As we verify that our technical implementation is sound, we hope to expand open access to more of the data.