Is BAWAG (AT) down right now?
No. BAWAG (AT) is working.
It answered our last check normally. If it still fails for you, the cause is more likely your device, app or network, or a problem limited to some regions or features. Checked 3 minutes ago · re-checked every 5 minutes
No outage in the last 30 days.
Get an email when BAWAG (AT) goes down
Checked every 5 minutes from independent probes. We also tell you when the cloud, CDN or DNS provider underneath BAWAG (AT) has an outage, and when it works again. No account, unsubscribe with one click.
What BAWAG (AT) runs on
Mapped from public DNS, network ownership and published cloud IP ranges. When one of these providers has an outage, BAWAG (AT) is exposed.
BAWAG (AT) endpoint
| Service | Status | Latency | 24h uptime |
|---|---|---|---|
| BAWAG (AT)www.bawag.at | up | 319 ms | 100% |
Recent incidents
No BAWAG (AT)-related provider incident detected in the last 7 days.
Services on the same providers as BAWAG (AT)
These services do not depend on BAWAG (AT), and a problem at BAWAG (AT) itself does not affect them. They use the same provider underneath, so an outage of that provider can hit them and BAWAG (AT) at the same time. If several of them are down together with BAWAG (AT), the shared provider is the likely cause.
Same DNS provider or CDN
Same name servers or content delivery network. An outage there makes all of these hard to reach at once.
Same cloud provider, region unknown
Same cloud company, but we could not confirm the same region. They are only hit together if that provider fails broadly, which is rare.
How we check BAWAG (AT)
Is this BAWAG (AT)'s official status page?
No. It is an independent, outside-in view. Official status pages often confirm incidents late; we probe real service endpoints every five minutes and publish what we see.
When do you say BAWAG (AT) is down?
A single failing request is reported as an error, never as an outage. A service is down after two consecutive failed checks, and we declare a provider incident only when several independent services that share the same provider fail together.
Why do other services appear here?
Because they use the same hosting, DNS or CDN provider as BAWAG (AT). They do not depend on BAWAG (AT). When that shared provider has problems, these services can be affected at the same time as BAWAG (AT), even if their own status pages still say everything is fine.
Watch your whole stack, not one service
Slack, Teams, webhook or email alerts for up to 25 services and the providers underneath them, early warnings, certificate and domain expiry. 14 days free, then $29 a month.
More live status pages · Payments & fintech
Independent monitoring by ShadowGraph. Not affiliated with or endorsed by BAWAG (AT). All trademarks belong to their owners.