Provide a feed of all edge IPs for endpoint firewall configuration

[bmertens-datum]

Proposal: Provide a feed of all edge IPs for endpoint firewall configuration

Customers need a reliable way to discover and maintain the list of our edge IP addresses so they can configure endpoint firewalls, allowlists, and egress controls without manual copying from docs or support tickets.

Right now, there isn’t a clear, machine-readable source of truth for “all current edge IPs,” which makes automation and ongoing maintenance harder.

---

What problem are we solving?

• Customers want to allow traffic to/from Datum in endpoint firewalls.
• IPs can change as we add PoPs/regions or rotate infrastructure.
• Manual lists in docs or emails don’t scale and are easy to get out of date.

We should provide a machine-readable feed that can be consumed by scripts, and firewall platforms.

---

Requirements (high level)

• Single source of truth for all public edge IPs / ranges (ingress + egress where applicable).
• Machine-readable formats (e.g. JSON, possibly CSV or plain text).
• Stable, documented URL(s).
• Metadata such as last_updated or version.
• Coverage for:
  • IPv4 and IPv6
  • All active regions/PoPs
  • (Optional) Labels for type: proxy, DNS, API, etc.

---

Possible approaches

1. HTTPS endpoint (primary)

   • Public endpoint such as:
     https://edge.datum.net/ip-ranges.json
   • JSON structure may include:
     • ipv4_ranges, ipv6_ranges
     • Optional region, service, purpose
     • last_updated, version

2. Plain-text / CSV vari

• Additional endpoints:
  • .../ip-ranges.txt (one CIDR per line)
  • .../ip-ranges.csv
• Useful for platforms that don’t handle JSON well.

3. Status / docs integration
   • Link the feed from:
     • Public documentation (“Firewall / allowlist configuration”)
     • Status page (if appropriate)
   • Include examples for Linux, Windows, MDM systems, and common firewall vendors.

---

Security / correctness considerations

• Define how quickly feeds are updated when:
  • Adding/removing PoPs
  • Scaling or reallocating IP ranges

---

Open questions

• What level of granularity is most useful for customers (by region, by service, by purpose)?
• Are there vendor-specific formats we should consider supporting?