Skip to content

bgpcanary 1.7.4

Choose a tag to compare

@github-actions github-actions released this 12 Nov 17:00
· 3 commits to main since this release

Added

  • Around this event. Every event page now opens with what else went on in the half hour either side of the event, whether or not it raised an event of its own:

    • what the routes did: how many RIS peers changed their path, when, and where they went ("56 moved from AS64510 → AS64496 to AS64512 → AS64496"), and the peers per upstream at both ends of the window. A transit dropping out behind one of your upstreams shows here even when too few peers changed upstream for an upstream-shift alert;
    • the RIPE Atlas ping rounds that stood out, each held against what's usual for that address (some probes never answer; that's allowed for), with a round whose replies took twice as long as usual marked too;
    • every other event of that window, whatever its kind, the info ones and the ones found during a backfill included;
    • the stretches bgpcanary didn't hear live, so a quiet line isn't taken for a quiet network.

    A long event gets the half hours around its start and around its end. The same lines open the text report, so they reach the API's and the MCP server's report too.

  • A tree on every event page. An event that names none of your prefixes (a reachability loss on a carrier's link address, a Path finder watch) now shows the path tree replay, the charts, the "who carried" table and the raw updates of your prefix (with several, the one whose routes changed most around the event). That's usually where the cause of such an event shows: until now its page had no BGP on it at all.

Changed

  • The strip under the tree shades every warning and critical event, not only outages, and the ones that name no prefix on every prefix's tree. Events that overlap share one shade. An event too short to see as a band (seconds, on a day's strip) gets a mark on top of the strip, and pointing at the strip says which events are there.
  • Event pages load faster. The routes at the moments a page shows are read from the stored history once, where they were read once per moment: on a history of 240,000 updates an ordinary event's page took about half as long.
  • The event page's "Related events" line is now the "Other events" part of Around this event.

Fixed

  • Event page: the AS paths listed for the moment the upstream mix changed most were half a minute old. They were those of that bucket's start, while the numbers in the table above them are those of its end, so a sharp change showed the old paths under the new counts.

Update a server install with sudo bgpcanary-update. Container image: ghcr.io/gregsowell/bgpcanary:1.7.4 (with Docker Compose: docker compose pull && docker compose up -d).
New installs: docs/INSTALL.md for a server, docs/DOCKER.md for a container.