eBill outages and problems
User reports, last 24 hours
No reports in this window
No problem reports came in for eBill in the last hour, and at this time of day there are usually almost none. The last spike in reports was 57 h ago and lasted 18 min.
- NormalClose to the usual level24 h · 0 reports
- ElevatedMore than 1.5 times the usual levelNone in this chart
- OutageMore than twice the usual level and far above the day's averageNone in this chart
- Usual levelWhat a usual day sees at that timeAlmost none at this time of day
No user reports came in for eBill in the past 24 hours, and its uptime over that window is 100.00%.
No 15-minute window had any reports at all, so the chart above stays flat.
eBill in November 2026
- Problem reports in November
- 72
Monthly report for November 2026
What went wrong
What people said was wrong in recent problem reports for eBill.
Share of 11 recent reports that said what was wrong.
eBill problem spikes, last 30 days
In the last 30 days, eBill had no outage spikes, but 1 period of elevated reports.
- Mon 12 Oct: 1 report
- Tue 13 Oct: 1 report
- Wed 14 Oct: 1 report
- Thu 15 Oct: 0 reports
- Fri 16 Oct: 1 report
- Sat 17 Oct: 0 reports
- Sun 18 Oct: 6 reports
- Mon 19 Oct: 1 report
- Tue 20 Oct: 0 reports
- Wed 21 Oct: no data
- Thu 22 Oct: 0 reports
- Fri 23 Oct: 1 report
- Sat 24 Oct: 0 reports
- Sun 25 Oct: 0 reports
- Mon 26 Oct: 0 reports
- Tue 27 Oct: 0 reports
- Wed 28 Oct: 1 report
- Thu 29 Oct: 9 reports
- Fri 30 Oct: 1 report
- Sat 31 Oct: 0 reports
- Sun 1 Nov: 0 reports
- Mon 2 Nov: 0 reports
- Tue 3 Nov: 1 report
- Wed 4 Nov: 0 reports
- Thu 5 Nov: 0 reports
- Fri 6 Nov: 1 report
- Sat 7 Nov: 2 reports
- Sun 8 Nov: 66 reports (elevated reports that day)
- Mon 9 Nov: 2 reports
- Tue 10 Nov: 0 reports
-
Elevated reports
Sun 8 Nov, 10:01–10:19Lasted 18 min10peak reports
A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. Monthly reports for all services
How to fix eBill not working
eBill is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:
Your browser tries to reach ebill.ch over your own connection, right now. Nothing is sent to us or stored.
Refresh your eBill list
Open the banking app or e-banking site where you receive bills and pull down on the list to refresh. If a new bill was just issued, it can take a few minutes to appear. Close the app completely and open it again if the list stays empty.
Check eBill activation in your bank
In your bank's e-banking, open the eBill area and confirm the account is linked to the service. Look under Messages or Settings if you cannot find it. If activation is off, turn it on and wait for the bank to confirm.
Update your eBill app
Install the latest version of the eBill app or your banking app from your phone's app store. Old builds can fail to load bills after a bank changes its login flow. On Android, open Settings, Apps, pick the app, then Storage and clear cache; on iPhone, offload the app and reinstall it from the App Store.
Contact the eBill help centre
If bills still do not load or a QR bill will not scan, send the help centre your bank name, phone model, app version, and a screenshot of the screen where it stops. You can also ask your bank's support whether your account needs a fresh activation. Include the exact time you tried and the steps you took before the error.
While eBill is down: what to use instead
- Manual payment in e-banking If you have the invoice by email or on paper, pay it as a normal payment order in your bank's e-banking with the IBAN and reference number printed on it.
- Scan the QR-bill Most Swiss banking apps can scan the QR code on a paper or PDF bill, which fills in the payment details for you.
- Your provider's customer account Many billers post the same invoice as a PDF in their own online portal, so log in there to see the amount and due date.
- Bank website instead of the app When the eBill section won't load in your mobile banking app, open your bank's e-banking in a browser, since the problem is sometimes limited to one of the two.
Fix eBill on Windows, Mac, Android and iPhone
eBill on Windows
- Fix
- Clear your browser's cache and cookies, or try accessing the eBill portal using an Incognito window in Chrome or Edge. Ensure your browser is updated to the latest version to support secure billing protocols.
- Check
- Attempt to load the eBill login page on a different web browser to see if the issue is browser-specific. You can also use the network diagnostics tool to check if the eBill server is reachable.
ping ebill.chTest whether eBill's servers replynslookup ebill.chCheck that eBill's DNS resolvestracert ebill.chTrace where the connection dropsipconfig /flushdnsClear the DNS cache, then reloadeBill on Mac
- Fix
- Clear Safari's website data in Safari settings, or try accessing eBill using an alternative browser like Chrome. Ensure any active VPNs or security software on your Mac are temporarily disabled, as they can block eBill connections.
- Check
- Check if the eBill website displays a specific HTTP error code or fails to load entirely in your Mac's browser. You can also try connecting to a different network to see if the eBill outage is local to your router.
ping -c 4 ebill.chTest whether eBill's servers replynslookup ebill.chCheck that eBill's DNS resolvestraceroute ebill.chTrace where the connection dropssudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderFlush the macOS DNS cache, then reloadeBill on Android
- Fix
- Clear the cache for your eBill-integrated banking app in your Android settings, or check the Google Play Store for updates. Restarting your device can also resolve temporary connection and credential conflicts.
- Check
- Verify if the eBill portal loads when switching your Android device from Wi-Fi to mobile data. If the app hangs on the loading screen or shows a network error, the eBill service may be down.
eBill on iPhone and iPad
- Fix
- Force close and relaunch your banking or eBill app, or check the App Store to ensure you have the latest version installed. If the problem persists, reinstalling the app on your iPhone or iPad can resolve configuration issues.
- Check
- Check if you receive a connection timeout error when trying to access eBill via Safari or your banking app on iOS. You can also check if other iOS users are reporting eBill disruptions on social media.
Problems at the same time as eBill
In the last 30 days, eBill's only spike in problem reports overlapped a spike at another service.
When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.
During the latest spike
eBill: Sun 8 Nov, 10:01 to 10:19
- Vivo, outage,03:33 to 13:07
- Shaw, outage,03:55 to 11:46
- Wells Fargo, outage,07:12 to 11:48
- Odido, outage,08:14 to 16:14
- Xfinity by Comcast, outage,08:25 to 11:01
- Tele2, outage,09:16 to 10:24
- GitHub, outage,09:38 to 14:31
- Ben, outage,09:38 to 15:01
13 more services. Red dot: outage. Amber dot: elevated reports.
A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.
When people report eBill problems
The busiest hour for reports about eBill is 10:00 to 11:00 Central European time, and the busiest day is Sunday.
By hour of the day
- 00:00 to 01:00: 0 reports on an average day
- 01:00 to 02:00: 0 reports on an average day
- 02:00 to 03:00: 0 reports on an average day
- 03:00 to 04:00: 0 reports on an average day
- 04:00 to 05:00: 0 reports on an average day
- 05:00 to 06:00: 0 reports on an average day
- 06:00 to 07:00: 0 reports on an average day
- 07:00 to 08:00: 0.03 reports on an average day
- 08:00 to 09:00: 0.21 reports on an average day
- 09:00 to 10:00: 0.47 reports on an average day
- 10:00 to 11:00: 0.53 reports on an average day
- 11:00 to 12:00: 0.4 reports on an average day
- 12:00 to 13:00: 0.23 reports on an average day
- 13:00 to 14:00: 0.21 reports on an average day
- 14:00 to 15:00: 0.09 reports on an average day
- 15:00 to 16:00: 0.14 reports on an average day
- 16:00 to 17:00: 0.23 reports on an average day
- 17:00 to 18:00: 0.09 reports on an average day
- 18:00 to 19:00: 0.12 reports on an average day
- 19:00 to 20:00: 0 reports on an average day
- 20:00 to 21:00: 0.03 reports on an average day
- 21:00 to 22:00: 0.06 reports on an average day
- 22:00 to 23:00: 0.14 reports on an average day
- 23:00 to 00:00: 0.09 reports on an average day
By day of the week
- Monday: 0.74 reports on an average Monday
- Tuesday: 0.34 reports on an average Tuesday
- Wednesday: 3.2 reports on an average Wednesday
- Thursday: 2.4 reports on an average Thursday
- Friday: 0.8 reports on an average Friday
- Saturday: 0.4 reports on an average Saturday
- Sunday: 14 reports on an average Sunday
Each bar is the average number of user reports in that hour, or on that day of the week, from 34 days of reports since 5 October 2026. The busiest bar is highlighted. Spikes in reports are left out, so one outage does not set the pattern.
What happens when eBill goes down
You pay through banks. eBill is the Swiss system that sends bills to your e-banking where you click to pay, so an outage stops delivery and leaves dues unpaid.
The inbox from your bank login loads blank or stalls because the redirect to the portal fails before bills appear. You cannot approve bills. PDF previews and standing approvals drop next while lookups of past receipts still open, so you see a half-dead service rather than a full blackout. Because it rides inside each bank's e-banking, trouble hits one bank portal while another stays up and you must retry or pay by slip.
eBill IP address, servers and network
- IPv4 address
- 153.46.97.4
- IPv6
- Not offered
- Network
- AS9042 · SIX Group Services AG, registered in the United States
- DNS hosted by
- Akamai
- HTTPS certificate
- Issued by SwissSign AG, valid until 19 Nov 2026 (8 days)
- HTTP/3
- Not advertised
- Our check
- Answered in 202 ms
Checked from our server in Frankfurt, Germany, 2 days ago, for www.ebill.ch. Visitors elsewhere may see different addresses.
Checked from 12 places around the world
All 12 locations got an answer from www.ebill.ch. Fastest from Frankfurt (62 ms), slowest from Tokyo (1,177 ms). Every location connected to the same address, on SIX Group Services AG (AS9042).
| Location | Result | Time | Address reached |
|---|---|---|---|
| FrankfurtGermany | Up · HTTP 301 | 62 ms | 153.46.97.4 |
| ViennaAustria | Up · HTTP 301 | 97 ms | 153.46.97.4 |
| MilanItaly | Up · HTTP 301 | 73 ms | 153.46.97.4 |
| ParisFrance | Up · HTTP 301 | 106 ms | 153.46.97.4 |
| AmsterdamNetherlands | Up · HTTP 301 | 111 ms | 153.46.97.4 |
| MadridSpain | Up · HTTP 301 | 208 ms | 153.46.97.4 |
| WarsawPoland | Up · HTTP 301 | 180 ms | 153.46.97.4 |
| DallasUSA | Up · HTTP 301 | 867 ms | 153.46.97.4 |
| Los AngelesUSA | Up · HTTP 301 | 547 ms | 153.46.97.4 |
| São PauloBrazil | Up · HTTP 301 | 655 ms | 153.46.97.4 |
| SingaporeSingapore | Up · HTTP 301 | 816 ms | 153.46.97.4 |
| TokyoJapan | Up · HTTP 301 | 1,177 ms | 153.46.97.4 |
Checked with check-host.net from its servers in these cities 2 days ago, for www.ebill.ch. Time is how long each server took to load the page.
eBill FAQ
Is eBill down right now?
Why do my bills stop appearing after I change banks?
I can see my invoice but I cannot approve it, what blocks me?
Login to eBill through my bank keeps failing, how do I get in?
What should I do when an approved bill never gets paid?
Contact eBill support
Tip: eBill doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.
About eBill
- Category
- Digital Billing
- Country
- Switzerland
How we track eBill
The status on this page comes from user-submitted problem reports for eBill, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for eBill, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.
When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. eBill doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.