Service status · OULY City
We have an outage.
Something you need is not working right now.
The rows marked UNKNOWN (7) were not measured just now – some cannot be measured from the outside, for others no answer arrived. Each one says why – and we never fill any of them in as WORKING.
I can see the city
Browsing cities, the map and finished visions.WEB
The ouly.city website
WORKING
Whether the website is deployed and answers from the internet. We do not test the rendering of individual pages from here.
The website answers a check address. · 528 ms
API
Our servers
WORKING
They answer everything the website and the app ask for. We measure their check address and the database connection, not every call separately.
The servers answer. · 707 ms
DBS
The database
WORKING
It holds the stored visions, pulses, accounts and cities. The time beside the row is the whole round trip from here, not the database’s own speed.
The database answers a check connection. · 699 ms
LST
The list of cities and boundaries
DOWN
Without it the map does not know where a city begins and ends.
We could not load the list of cities. · 660 ms
MAP
Map tiles
WORKING
They draw the base map on the web and in the app.
Map tiles are loading. · 440 ms
IMG
Photos and vision images
UNKNOWN
Public reading of photographs and generated visions.
We have not been told where to ask. We do not know.
I can create a vision
The path from a resident’s idea to a finished vision.BUD
Today’s budget for visions
UNKNOWN
How many visions the live cities’ budgets will still pay for today, added up. One person may create at most five a day.
We did not get the list of live cities, so we claim nothing about the budget. · 657 ms
VIS
Creating a vision from start to finish
UNKNOWN
The conversation with the assistant, generating the image and checking the content.
We do not run the whole path from here: one test vision costs money out of a city’s budget and would take a resident’s place. So we claim nothing about it.
I can sign in
Accounts, signing in and confirming an address.AUT
Signing in
DOWN
Accounts, signing in by e-mail, with Google and with Apple.
The sign-in service answers differently than it should. · 634 ms
RTE
Signing in from a browser and from the app
WORKING
The path sign-in takes through ouly.city. If it falls, nobody signs in anywhere.
The path through the website answers. · 814 ms
GOO
Signing in with Google
WORKING
The “Continue with Google” button on the sign-in screen.
Google answers on the sign-in path. · 434 ms
APL
Signing in with Apple
WORKING
The “Continue with Apple” button – required in the iPhone app.
Apple answers on the sign-in path. · 475 ms
E-mail reaches me
Confirmations, password resets and news.LNK
The links in our e-mails
UNKNOWN
Whether the e-mail paths on our servers are running. We test the newsletter unsubscribe link; confirming an address and resetting a password are not tested from here.
The e-mail links answered unexpectedly, so we claim nothing about them. · 650 ms
DLV
Delivery to the inbox
UNKNOWN
Whether an e-mail actually reached the person it was sent to.
Delivery is only visible in our mail partner’s own reply, and we do not read that from here. At least its own status is listed below.
The app
What the server can tell us about the mobile app, and what it cannot.UPL
Photo upload from the app
WORKING
A photo from a phone travels to our servers by its own path, outside the website.
The path from the app answers. · 679 ms
DEV
The app on phones
UNKNOWN
Version, crashes and native layers on the device itself.
What happens on one particular phone is invisible from our servers. The app sends its version and its errors to our analytics, not here – and this page deliberately does not read analytics. We do not know.
Our cities
Where OULY City runs. This is not outage measurement, it is an overview of coverage.CIT
Cities
UNKNOWN
Where OULY City runs.
We did not get the list of cities just now, so there is nothing to list here. · 660 ms
What we stand on
What the companies we stand on say about themselves. Their state does not decide the overall state of this page.
VercelHosts the website, this page, and the path the mobile app takes to our servers. The supplier reports that everything works.Their page ↗RailwayHosts our servers. The supplier reports that everything works.Their page ↗NeonHosts our database. The supplier reports that everything works.Their page ↗CloudflareHolds the photos and the vision images. The supplier reports a problem on their side.Their page ↗OpenAIRuns the conversation, draws the visions, transcribes recordings and checks the content. The supplier reports that everything works.Their page ↗ResendDelivers our e-mails. The supplier reports that everything works.Their page ↗Trigger.devRuns the background work – drawing visions, nightly recalculations, campaigns. The supplier reports that everything works.Their page ↗ExpoDelivers updates to the app. The supplier reports that everything works.Their page ↗
OpenFreeMapDraws the base of every map – on the website and in the app. OpenFreeMap is a non-commercial project with no status page and no feed we could read. So we claim nothing about its own state; whether the tiles reach us is measured by the “Map tiles” row above.
Google MapsThe photo map – satellite imagery of the city. For Maps Platform, Google publishes only a history of incidents, not an indicator of the current state. Deriving a state from history would not be a measurement, so we claim nothing about it.
What this snapshot measured
- Whether our servers, the database, the image storage and the map tiles answer – and how fast.
- Whether the public sign-in paths and the links in our e-mails answer the way they should.
- How many visions the live cities’ budgets will still pay for today, added up.
- What our suppliers’ own status pages say about themselves.
What we do not measure
- Whether a particular vision actually gets made. We cannot test the whole path – conversation, image, content check – from the outside without spending a city’s budget.
- Whether an e-mail actually reached the inbox.
- How the app behaves on the phone itself.
- Anything from the past. We do not store check results, so this page knows only the present moment.
How to read this
- Every row is one measurement taken at the moment printed above. Nothing is smoothed and nothing is filled in.
- You will not find an uptime percentage here. We do not store a history of checks, so every “99.9%” would be made up.
- When a probe does not answer in time, or a thing cannot be measured from the outside, the row is UNKNOWN. We never fill it in as WORKING.
- The state at the top is the worst of what we actually measured. UNKNOWN rows neither turn it green nor red – they are listed separately.
- This page is served by a different provider than our servers. That is how it can also tell you that our servers are down.
- A supplier’s state is taken from their own page. It describes their whole platform, not our slice of it, so it does not decide the overall state above.
- The measured times include our own overhead – all probes run at once. They are orders of magnitude, not a measurement from your browser.
- Measurements are valid for at most 60 seconds; after that they are taken again.
We do not store check results yet, so we have no history to show – no 90-day bar, no uptime percentage. Once we start storing it, the date of the first record will be written here.
If this page is unreachable too, write to info@ouly.city.