Issues

Atlas infers a lot, and inference is sometimes wrong: a geolocation that puts a probe in the wrong city, an anycast detection that misfires, a stale record. Issues — flags, in the UI — are how you say so.

/flags · requires an account

What a flag is

A flag is attached to a specific record rather than floating free. Every flag targets one document in one collection, and the collections you can flag are:

probes · anchors · measurements · asns · ips · domains · countries · regions

That targeting is the whole point. "The geolocation is wrong" is hard to act on; the same words attached to probe 6042 are a work item.

Each flag also carries:

• a type — issue, bug, todo, improvement, observation or ticket
• a priority — low, medium or high
• an optional due date
• a done toggle, which records who closed it and when

The type list is wider than "something is broken" on purpose: observation and todo let you record something worth remembering about a record without claiming it is a defect.

Private flags

A flag can be marked private, in which case it is visible only to its author and to admins. Use it for anything you would not put on a public record — otherwise leave flags public, since a visible flag is what stops two people investigating the same thing.

This is also why the whole Issues section needs an account: flags can be private, so there is no anonymous view of them.

Due dates and overdue

A due date is a calendar day, and a flag counts as overdue once that day has fully passed in UTC — not at the start of the day, and not in your local timezone. A flag due today is never overdue today.

Flags that are done are never overdue, whatever their due date.

Working with flags

The Issues page is a management view over everything you can see: filter by type, priority, status and target, and work down the list. Your open issues also surface on your dashboard, with comment counts, so you don't have to go looking.

Each flag has its own page at /flags/:id — the single place to edit it and the home of its comment thread. Discussion belongs there rather than in the flag body, so the description stays a statement of the problem.

Issues versus feedback

Use	For
Issues	The data is wrong — a bad location, a stale record, a misfired detection
Feedback	The product is wrong — a confusing view, a missing feature, a bug in the page itself

If you are pointing at a record, it is an issue. If you are pointing at a page, it is feedback.

---

See also: Geofeeds and geolocation, the area where flags are most often needed.