Deployment probe13f606f

Measured on this request

Outbound reach

The server called 5 public endpoints and 5 answered. Restricted egress is a common surprise after a deploy, and it fails in ways that look like application bugs.

Upstreams

6 second timeout each, never cached

  • GitHub API200 · 96ms

    https://api.github.com/zen

    HTTPS egress to a major API host

    Favor focus over features.

  • Postman Echo200 · 50ms

    https://postman-echo.com/get

    Full request/response round trip with JSON

    {"args":{},"headers":{"host":"postman-echo.com","sec-fetch-mode":"cors","user-agent":"node","accept-encoding":"gzip, br","cache-control":"no-cache","x-forwarded…

  • Cat Facts200 · 77ms

    https://catfact.ninja/fact

    A small third-party JSON API

    {"fact":"Cats have 300 million neurons; dogs have about 160 million","length":58}

  • Dog CEO200 · 144ms

    https://dog.ceo/api/breeds/image/random

    A CDN-backed JSON API

    {"message":"https://images.dog.ceo/breeds/vizsla/n02100583_2086.jpg","status":"success"}

  • JSONPlaceholder200 · 25ms

    https://jsonplaceholder.typicode.com/todos/1

    The classic fixture API (blocked on some networks)

    { "userId": 1, "id": 1, "title": "delectus aut autem", "completed": false }

Same data as JSON at /api/upstreams.