Bulutegra system status
This page shows the current status of the Bulutegra panel, the API, the marketplace connections, the ERP transfer and the website. It is updated automatically from our own checks.
Announcements
No announcements in the last 30 days.
Current status
Each bar is one day. Green: no problems · Orange: partial problem or delay · Red: downtime · Grey: not measured that day
All times are Türkiye time (GMT+3).
What this page shows
The page has three groups. Core platform: the seller panel, the Bulutegra API, webhooks, ERP order import and the product and stock feed from the e-commerce platform. Marketplace connections: the last successful stock and price sync for each channel, or the last successful order check where a channel has no stock sync. Web: the website, the developer portal and the demo environment. Carrier connections and conditions specific to a single account are not shown here; you see those in the system health screen inside your own panel.
Each row states its current status in words and with an icon: ✓ Operational, ! Delayed, ✕ Down. Every bar in the strip is one day: a full-height green bar means the day passed without problems, a short orange bar means a partial problem or delay during the day, a red bar with diagonal stripes means downtime, and a grey bar means no measurement was taken that day. Hover a bar to see the date and the ratio. The percentage under each row is the share of checks that passed in the last 60 days.
If a row looks degraded, something is getting in the way of reaching that service. On its own that does not say whether the cause is on our side or the channel's side; it can be either.
The page is public. You do not need to sign in to read it.
How it is measured
Measurement comes from checks our own servers run continuously. Each check confirms that a service is reachable and that it answers as expected.
This is our infrastructure checking itself, not an outside monitor. So what you see here says nothing about your own connection or local network. If you cannot reach the panel while this page looks normal, the problem is most likely somewhere in between; write to us and we will look at it with you.
Results are published as they come in. Nothing here is edited by hand.
What we do during an incident
If a channel stays silent for longer than expected, an alert is raised and the team responsible is notified. When an incident affects customer operations, we inform the affected accounts as well.
The panel also has a system health screen. There you look beyond the general picture at your own account's channels: which ones are exchanging data and which are waiting.
During an incident the order of priority is data integrity first, speed second. When a connection to a channel drops, pending work is not lost; it is processed once the connection returns. That is why you may see a short delay just after an incident.
How planned maintenance is announced
Planned maintenance is announced in advance. The announcement says when the work will happen, which parts it affects, and how long we expect it to take.
Wherever possible we schedule maintenance for hours when order traffic is low. During campaign periods we avoid planning maintenance unless it is unavoidable.
The maintenance window also appears on this page. When the work is finished the status returns to normal, with a short closing note where one is warranted.
When you see a problem
If this page looks normal but something is wrong on your side, tell us. This page reflects the general picture; a problem specific to one account or one channel may not show up here.
It helps to include the channel, the screen you were on, when you noticed the problem, and an order code or SKU if you have one.
Our address: [email protected]
Frequently asked questions
This page looks fine, but I cannot open the panel. What should I do?
Try another network or another browser first; this page only covers services on our side and does not measure your own connection. If it persists, write to [email protected] with the screen you were stuck on and the time it happened.
If a marketplace goes down on its side, does it show on this page?
Partly. The marketplace connections group shows each channel's last successful sync; if a channel cannot sync for longer than expected, its row turns Delayed. On its own that does not say whether the cause is on our side or the channel's side. When a connection drops, queued work is not lost; it is processed in order once the connection returns. When we can see the cause is on the channel's side, we tell the affected accounts.
Can I lose orders or stock updates during an incident?
No. Pending work is held in a queue and processed once the connection is back. You may see a short delay afterwards, and you can follow your own channels on the system health screen inside your panel.
Seeing a problem that is not reflected here? Write to [email protected].
See it before we explain it.
We will send you login details for a working copy of the panel; explore it yourself, then let’s talk.