Service status & support

For the “is this me, or is this the service?” moments, this page helps you decide whether to wait or to contact us — and how to describe the problem so we can answer in one round.

First: is it your side or ours?

There is no separate real-time status page yet, so run these three checks:

1. Try another environment — reproduce in a different browser / network / device. If only one environment fails, it is usually local (network, extension, browser version)
2. Read the delivery log — when reports do not reach your table, the delivery log under “Settings → Integrations” separates “your configuration” (credentials, permissions) from “service-side” (network failure, 5xx)
3. Wait and retry — occasional server-side failures usually heal themselves. When a submission fails, the content is still in your browser and is not lost; just retry

If several environments fail at the same time and it lasts more than a few minutes, it is most likely service-side — contact us.

Contact us

📮 bugcapturer@gmail.com

So that our first reply can already be an answer, please include:

Information	Why we need it
What you were doing (screenshot / recording / configuring an integration…)	Routes the report to the right module
Page URL and the time it happened	Lets us line it up with server logs
The full error message or a screenshot	“It errored” and “what the error says” are very different
Extension version (Settings → About) or SDK version	Rules out known issues in older versions

Ordinary questions get a reply within one business day; service incidents are prioritised.

Other channels

• Docs feedback — every page has a “Something wrong with this page?” button; it submits automatically with the page information attached
• Product suggestions — send them to the same email, marked “suggestion”

See also

• SDK & extension troubleshooting — self-check by symptom first
• FAQ
• Reporting abuse & takedown — for content abuse