INTASTELLAR SOLUTIONSHelp Center

System status

Automated HTTP checks from Intastellar Help. Machine-readable snapshot: /api/status.json.

How we measure uptime

Short notes so you know what this page represents.

  • Synthetic checks: automated HTTP requests from our hosting provider to each public URL below — not real-user (RUM) monitoring.
  • Schedule: production runs about once per minute (your project’s cron configuration).
  • A check passes when the HTTP status is below 500; timeouts and network errors count as failed.
  • Timelines, incident log, latency trends, and the headline uptime percentage use stored checks from the last 48 hours (UTC), up to 5000 samples per load (MongoDB TTL about 14 days). The headline figure also treats active operator notices and scheduled maintenance (when they apply) like downtime for that run.
  • All times on this page are UTC.

Scheduled maintenance

No in-progress or upcoming maintenance windows are published right now.

Last deploy

Commit

7ad53ae · View commit on GitHub

Branch

development

Message

Fixed. The reopen bubble's cookie icon brightness was hardcoded to contrast against window.INTA.settings.color (the general brand/accept color) — but for nova specifically, that bubble's background is forced to var(--inta-nova-card-bg) (i.e. novaBackgroundColor) by nova.css, a completely different color. So picking a white novaBackgroundColor kept the icon brightened to white while the bubble behind it went white too. In dev/cb.dev.js:2822 (where the reopen icon's <img> gets its inline filter: brightness(...)), it now checks the design: for "nova", it contrasts against novaBackgroundColor (falling back to nova's default navy #2b2a42 when unset) instead of the brand color; every other design is unchanged. Verified the underlying contrast logic with Node (darkLightCheck("#fff") → "light" → brightness 0, i.e. dark icon; default navy → "dark" → brightness 100, i.e. white icon, same as before) — no visual browser test, same limitation as last time (no Chrome/Playwright in this environment).

100% uptime

We run these checks automatically on a schedule. Over the last 48 hours (UTC), we stored 5000 runs · 5000 count as fully up: every service responded normally in that run, with no active operator notice or scheduled maintenance applying to that moment.

All checks passingUpdated Oct 17, 2026, 12:38 AM UTC (stored, UTC)

  • Intastellar Consents

    https://www.intastellarconsents.com

    Recent checks — last 48 hours (5000 samples)

    Response time (Intastellar Consents)

    Min 19 ms
    Max 1035 ms
    Latest 25 ms
    HTTP 20025 ms

  • Consents CDN (uc.js)

    https://consents.cdn.intastellarsolutions.com/uc.js

    Recent checks — last 48 hours (5000 samples)

    Response time (Consents CDN (uc.js))

    Min 17 ms
    Max 1044 ms
    Latest 25 ms
    HTTP 20025 ms

  • Intastellar Help — Help Center

    https://help.intastellarsolutions.com/

    Recent checks — last 48 hours (5000 samples)

    Response time (Intastellar Help — Help Center)

    Min 30 ms
    Max 1653 ms
    Latest 95 ms
    HTTP 20095 ms

  • Intastellar Consents — analytics collect (health)

    https://analytics.intastellarsolutions.com/collect?health=1

    Recent checks — last 48 hours (5000 samples)

    Response time (Intastellar Consents — analytics collect (health))

    Min 63 ms
    Max 2773 ms
    Latest 75 ms
    HTTP 20075 ms

Operator notices

Updates posted by the team when we communicate an issue or follow-up (separate from automated probe history below).

  • Intastellar Consents Platform: Issue accessing the platform when logged in

    We are currently having issues with routing of Intastellar Consents, which affects the view of our dashboards on intastellarconsents.com/gdpr/dashboard. We are working on implementing a solution, to solve the issue.

    Updates

    • Update · Apr 20, 2026, 8:50 AM UTC · felix.schultz@intastellar.com · Investigating → Resolved

      We fixed the issue. There where a miss configured file causing the 404 error

    Monitors: Intastellar Consents

    Posted by felix.schultz@intastellar.com · · Resolved

    Resolved

  • Intastellar Consents (CMP) Dashboard - CORS Errors

    We have noticed some CORS errors with our APIs for Intastellar Consents CMP platform - causing currently blank page on the dashboard. We are working on the situation to fix it as fast as possible. Consent collection is still working & we do not see any problems with these endpoints. Monitors: Intastellar Consents.

    Updates

    • Update · Apr 6, 2026, 7:52 PM UTC · felix.schultz@intastellar.com · Identified → Resolved

      We fixed the issue - some header requests weren´t allowed to connect. Which caused the API´s to be blocked on the request. Everything is resolved & the Intastellar Consents dashboard, is up an running again.

    Monitors: Intastellar Consents

    Posted by felix.schultz@intastellar.com · · Resolved

    Resolved

Incident log

An incident is a stored cron run where at least one target was down (HTTP 5xx, timeout, or no response — same rules as the live checks). If everything in recent history passed, this list stays empty.

Footnote — hosting and configuration

This page is public. The details below are for teams that deploy Intastellar Help (environment variables, data retention).

Configure targets with STATUS_CHECK_TARGETS_JSON (full replace) or STATUS_CHECK_EXTRA_JSON (append). A check counts as passing when the HTTP status is below 500. The incident log shows stored cron runs where any target failed in that window, including probe error text when saved. Timelines, the incident log, and latency trends use the same rolling store: the last 48 hours (UTC), up to 5000 samples per request (14-day TTL in Mongo). The headline uptime percentage uses the same window: runs count as up only when every target passed and the run time is outside operator notices and maintenance windows that apply (global or to those targets). Tune with STATUS_HISTORY_WINDOW_HOURS and STATUS_HISTORY_MAX_ROWS. Times on this page are UTC. New history rows store per-target latencyMs; older rows still drive up/down segments until they expire.