Service status

Is Vampelium working?

This is the page that will answer that question. It cannot answer it yet, because nothing is measuring our services at the moment — so rather than show you a page full of reassuring green ticks that mean nothing, we have left it honest and explained exactly what will appear here.

Read this first

There is no live data on this page. None of it.

A status page is only worth reading if the numbers on it come from somewhere. Ours do not yet: no monitoring system is connected to this page. Nothing is checking whether VampAuth can issue a sign-in, whether VampStore is serving files, or whether VampAI is responding.

That means there is no uptime percentage on this page, no response time, no incident history and no “all systems operational” badge. Those things exist on other companies’ status pages because a system somewhere is taking measurements. Publishing them without measurements is not a placeholder — it is a made-up record, and it would be the first thing you found out we had lied about.

So the service list below reports one state, and the state is “not yet monitored”. It means exactly what it says: not that everything is fine, and not that anything is broken. It means nobody is looking.

Data source
Not connected No checks are running against any Vampelium service, so there is nothing to display.
Monitoring provider
[TO BE CONFIRMED: monitoring provider] We have not chosen who or what will run the checks. When we do, this is where it will be named — including whether it is a third party, so you know who is measuring us.
This page updates
By hand, for now It is a static page. It does not refresh, poll anything, or change while you are looking at it. When it is live, it will say when it last checked and how often it checks.
Numbers published
Zero No uptime figures, no latency, no historical graph. There will be none until something is measuring them.

The seven services

Everything we run, and what we can currently tell you about it.

These are the seven services behind a Vampelium account. Each row is where a real, measured state will appear. Until then every row says the same thing, because we know the same amount about all of them: nothing.

Live status region State: awaiting data source

  • VampAuth

    Your account: signing in, verifying your email, and the apps you have connected.

    Current state Not yet monitored
    Last checked Never — no checks are running

  • VampStore

    Your files and photos — uploading, opening and sharing them.

    Current state Not yet monitored
    Last checked Never — no checks are running

  • VampMessage

    Sending and receiving messages, and their delivery across your devices.

    Current state Not yet monitored
    Last checked Never — no checks are running

  • VampAI

    The assistant: answering questions and working with the things in your account.

    Current state Not yet monitored
    Last checked Never — no checks are running

  • VampSecurity

    Protection around your account: unusual sign-in checks and session alerts.

    Current state Not yet monitored
    Last checked Never — no checks are running

  • VampData

    Keeping your things in step across every device you are signed in on.

    Current state Not yet monitored
    Last checked Never — no checks are running

  • VampCompute

    The processing underneath the rest — the part that makes everything else quick.

    Current state Not yet monitored
    Last checked Never — no checks are running

This frame is reserved. The seven rows above are the exact shape real measurements will take — when [TO BE CONFIRMED: monitoring provider] is connected, each row’s state and “last checked” fill in from live checks, and this note is removed.

Incidents

Incident history.

Incident feed region State: awaiting data source

No incident history is being kept yet

An empty incident list normally means a calm few months. Here it means the record does not exist: nothing is recording outages, so there is nothing to list — not even the ones that may already have happened.

Once monitoring is connected, this space fills with entries in plain language, newest first: what broke, roughly how many people it affected, what we did, and when it was fixed. We will write them for people, not for engineers, and we will leave them up afterwards rather than quietly deleting the bad weeks.

When it is live

What this page will actually tell you.

Not a wall of graphs. The six things you would actually want to know if something you rely on stopped working.

  • Whether it is us or you

    The first question anyone has. Each service will carry a current state in plain words, so you can tell within seconds whether to keep restarting your phone or to go and make a coffee instead.

  • When we last looked

    A state with no timestamp is a rumour. Every row will say when it was last checked and how often checks run, so you can tell the difference between “fine a moment ago” and “fine at some point last week”.

  • What is broken, while it is broken

    Open incidents will appear at the top of this page with what we know so far, and be updated as we learn more — including the updates where the honest answer is that we do not know yet.

  • Work we have planned in advance

    Maintenance that will interrupt something gets posted here before it happens, with what will be unavailable and roughly for how long — not discovered after the fact.

  • What happened afterwards

    After anything significant, a short write-up in ordinary language: what went wrong, what it meant for you, and what we changed so that particular thing does not happen again.

  • Where the numbers come from

    Whatever ends up measuring us will be named on this page, along with what it actually tests. A status page that will not say how it knows is asking to be taken on faith.

The vocabulary

The states we will use, defined before we need them.

Writing these down now, while nothing is on fire, keeps us from inventing a comfortable new word for “broken” on the day it matters. None of them are in use yet — every service on this page currently sits outside this set, at “not yet monitored”.

  • Operational

    Checked recently, working as it should. This word will only ever appear next to a real check with a real timestamp.

  • Degraded

    Working, but not properly — slower than it should be, or failing some of the time. Usually the state you are in when something feels wrong but nothing has obviously broken.

  • Partial outage

    Part of the service is down while the rest keeps going — one feature, or one region, rather than the whole thing. We will say which part.

  • Major outage

    Down. Not slow, not partly working — unavailable for most people trying to use it.

  • Maintenance

    We took it offline on purpose and said so beforehand. If we did not say so beforehand, it is an outage, and we will call it one.

  • Not yet monitored

    The state every service is in today. Nothing is checking it, so we have no opinion about whether it is working — and we would rather say that than guess.

Colour will never be the only signal. Every state on this page is written out in words and carries its own shape, so it can be read in black and white, in high contrast mode, on a bad screen in sunlight, or by someone who does not distinguish red from green. That is deliberate — and it is also why there is no green tick anywhere on this page today.

In the meantime

If something is not working for you right now.

Since this page cannot tell you anything yet, here is what is actually worth doing — and where the honest gaps are.

  • Rule out your own connection first. Try another site, switch between Wi-Fi and mobile data, and reload once. It is unsatisfying advice and it is right more often than not.
  • If it is sign-in specifically, try signing in again in a fresh tab. If you never received a verification email, you can ask for a new code from the verification screen rather than creating a second account.
  • If a page will not let you do something at all — a control you cannot reach, a message you never hear — that may be an accessibility problem rather than an outage. Our accessibility statement lists the issues we already know about.
  • To report an outage: support@vampemail.com

Email delivery and monitoring for support@vampemail.com have not been verified. No phone or chat channel is currently listed. This page does not confirm whether any service is operational.

Why the page looks like this

An empty status page is a status.

The easy version of this page would have taken ten minutes: seven rows, seven green ticks, a made-up uptime figure with two decimal places on it, and a banner saying everything was fine. It would have looked more finished than this one does.

It would also have been a fabrication. Every number on it would have been typed by a person rather than measured by anything, and the first time one of these services actually went down, that page would have carried on saying everything was fine — which is the precise moment a status page either earns its place or proves it never had one.

So this page reports what we know. Right now that is: seven services exist, nothing is watching them, and here is what will change when something is. When the monitoring is connected, this page changes and the rows fill in with measurements. Until then, the emptiness is the accurate reading.