Systemstatus
Automatiserede HTTP-tjek fra Intastellar Help. Maskinlæsbar snapshot: /api/status.json.
Sådan måler vi oppetid
Korte noter om, hvad siden viser.
- Syntetiske tjek: automatiserede HTTP-forespørgsler fra vores udbyder til hver offentlige URL nedenfor — ikke RUM.
- Plan: i produktion ca. én gang i minuttet (dit projekts cron-konfiguration).
- Et tjek består, når HTTP-status er under 500; timeouts og netværksfejl tæller som fejl.
- Tidslinjer, incident-log, latenstrends og top-oppetidsprocent bruger gemte tjek fra de seneste 48 timer (UTC), op til 5000 prøver pr. indlæsning (MongoDB TTL ca. 14 dage). Aktive driftsmeddelelser og planlagt vedligehold tæller som nedetid i top-tallet, når de gælder.
- Alle tidspunkter på siden er UTC.
Planlagt vedligehold
Der er ikke offentliggjort igangværende eller kommende vedligeholdelsesvinduer lige nu.
Seneste deploy
Commit
7ad53ae · Se commit på GitHub
Branch
development
Besked
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% oppetid
Vi kører disse tjek automatisk efter en tidsplan. I de seneste 48 timer (UTC) blev der gemt 5000 kørsler · 5000 regnes som fuldt oppe (alle tjenester svarede normalt i kørslen, uden gældende driftsmeddelelse eller vedligehold på det tidspunkt).
Intastellar Consents
https://www.intastellarconsents.com
Seneste tjek — seneste 48 timer (5000 prøver)
Svartid (Intastellar Consents)
Min 19 msMaks 1035 msSeneste 24 msHTTP 20024 msConsents CDN (uc.js)
https://consents.cdn.intastellarsolutions.com/uc.js
Seneste tjek — seneste 48 timer (5000 prøver)
Svartid (Consents CDN (uc.js))
Min 17 msMaks 1044 msSeneste 27 msHTTP 20027 msIntastellar Help — Help Center
https://help.intastellarsolutions.com/
Seneste tjek — seneste 48 timer (5000 prøver)
Svartid (Intastellar Help — Help Center)
Min 30 msMaks 1653 msSeneste 65 msHTTP 20065 msIntastellar Consents — analytics collect (health)
https://analytics.intastellarsolutions.com/collect?health=1
Seneste tjek — seneste 48 timer (5000 prøver)
Svartid (Intastellar Consents — analytics collect (health))
Min 63 msMaks 2773 msSeneste 86 msHTTP 20086 ms
Driftsmeddelelser
Opdateringer fra teamet om hændelser eller opfølgning (adskilt fra automatisk probe-historik nedenfor).
- Løst
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.
Opdateringer
Opdatering · Apr 20, 2026, 8:50 AM UTC · felix.schultz@intastellar.com · Undersøger → Løst
We fixed the issue. There where a miss configured file causing the 404 error
Overvågninger: Intastellar Consents
Skrevet af felix.schultz@intastellar.com · · Løst
- Løst
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.
Opdateringer
Opdatering · Apr 6, 2026, 7:52 PM UTC · felix.schultz@intastellar.com · Identificeret → Løst
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.
Overvågninger: Intastellar Consents
Skrevet af felix.schultz@intastellar.com · · Løst
Incident-log
Et incident er en gemt cron-kørsel hvor mindst ét mål var nede (HTTP 5xx, timeout eller intet svar — samme regler som live-tjek). Hvis al nyere historik bestod, forbliver listen tom.