Server down?
Answered
Anyone else having problem accessing https://my.zipato.com today?
I just get a white blank page.
Tried several computers and also tried re-powering my zipato (have green steady light).
Also problem with my android app now. Get "something went wrong" / "device cannot communicate properly with the server or Zipabox".
The same question
No connection
Real-time notifications may not work
Mine is working fine.
Mine is working fine.
same problem here. seems some servers are down
same problem here. seems some servers are down
same problem here.
same problem here.
Just checked, mine is also down.
Just checked, mine is also down.
i cant connet too
i cant connet too
Hi,
The monitor Zipato (https://my.zipato.com/zipato-web/Dashboard#) is back UP (HTTP 200 - OK) (It was down for 1 hour, 0 minutes and 34 seconds).
Hi,
The monitor Zipato (https://my.zipato.com/zipato-web/Dashboard#) is back UP (HTTP 200 - OK) (It was down for 1 hour, 0 minutes and 34 seconds).
Cool Down Guys....it was a Line Problem:
7. 80.150.168.162 0.0% 1182 25.0 24.9 24.3 56.4 2.6
8. hbg-bb1-link.telia.net 0.0% 1182 24.8 28.2 24.4 140.3 12.0
9. ldn-bb3-link.telia.net 3.1% 1182 62.4 62.4 58.3 145.2 5.2
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
10. ldn-b1-link.telia.net 1.5% 1182 68.6 62.9 60.1 78.6 1.3
11. a100-ic-314170-ldn-b1.c.telia.net 1.4% 1182 62.4 62.9 59.9 97.8 3.2
12. ???
13. ???
14. 176.32.106.14 95.9% 1181 78.5 77.3 75.5 78.6 0.7
15. 176.32.106.71 2.2% 1181 74.0 73.7 70.4 92.9 1.3
178.236.0.103
176.32.106.51
178.236.0.83
16. 178.236.0.110 2.4% 1181 74.9 71.9 68.3 86.3 1.8
178.236.0.114
17. 178.236.0.58 1.4% 1181 70.0 70.0 67.2 88.8 1.3
18. ec2-54-246-189-47.eu-west-1.compute.amazonaws.com 1.8% 1181 70.3 70.2 67.4 86.3 1.0
I think the Provider Telia had an Routing Problem....
regards Helle
Cool Down Guys....it was a Line Problem:
7. 80.150.168.162 0.0% 1182 25.0 24.9 24.3 56.4 2.6
8. hbg-bb1-link.telia.net 0.0% 1182 24.8 28.2 24.4 140.3 12.0
9. ldn-bb3-link.telia.net 3.1% 1182 62.4 62.4 58.3 145.2 5.2
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
ldn-bb3-link.telia.net
10. ldn-b1-link.telia.net 1.5% 1182 68.6 62.9 60.1 78.6 1.3
11. a100-ic-314170-ldn-b1.c.telia.net 1.4% 1182 62.4 62.9 59.9 97.8 3.2
12. ???
13. ???
14. 176.32.106.14 95.9% 1181 78.5 77.3 75.5 78.6 0.7
15. 176.32.106.71 2.2% 1181 74.0 73.7 70.4 92.9 1.3
178.236.0.103
176.32.106.51
178.236.0.83
16. 178.236.0.110 2.4% 1181 74.9 71.9 68.3 86.3 1.8
178.236.0.114
17. 178.236.0.58 1.4% 1181 70.0 70.0 67.2 88.8 1.3
18. ec2-54-246-189-47.eu-west-1.compute.amazonaws.com 1.8% 1181 70.3 70.2 67.4 86.3 1.0
I think the Provider Telia had an Routing Problem....
regards Helle
Sorry but that would be incorrect. People from different countries are routed differently to amazon (this is where zipato is hosted)
I am not routed via telia, but that's because i live in a different country. My scenario is just 11 hops and yours is 18 for example (if the numbers are correct in your post)
Sorry but that would be incorrect. People from different countries are routed differently to amazon (this is where zipato is hosted)
I am not routed via telia, but that's because i live in a different country. My scenario is just 11 hops and yours is 18 for example (if the numbers are correct in your post)
I just heard from some Users that they can connect.......my fault
I just heard from some Users that they can connect.......my fault
I am down
I am down
Some statistics (not executed from my home but external in the USA)
As you can see the uptime is quite OK
Some statistics (not executed from my home but external in the USA)
As you can see the uptime is quite OK
Mine is down again.
Mine is down again.
My box is offline too
My box is offline too
Mine to
Mine to
My box is still not responding correctly.
My box is still not responding correctly.
Hallo!
As there is no update from zipato I assume there are ongoing problems.
Events seem to be delayed a few minutes. eg. I open a door and it takes a few minutes to see the event in my.zipato.com.
@Milan Gulis: Can you give us an update. Server problems for more than 24 hours.......
regards,
bernhard
Hallo!
As there is no update from zipato I assume there are ongoing problems.
Events seem to be delayed a few minutes. eg. I open a door and it takes a few minutes to see the event in my.zipato.com.
@Milan Gulis: Can you give us an update. Server problems for more than 24 hours.......
regards,
bernhard
Amazon EC2 Maintenance Help Page
We frequently upgrade our Amazon Elastic Compute Cloud (EC2) fleet, with many patches and upgrades being applied to instances transparently. However, some updates require a short instance reboot in order to apply these updates. This page provides information on the reboot process.
The recent release of our scheduled events functionality provides greater visibility into the timing of these reboots. In addition to added visibility, in most cases you can use the scheduled events to manage reboots on your own schedule if you want to reboot before the scheduled update window. You can easily view any upcoming scheduled events for your instances in the AWS Management Console or using the API tools or command line. Reboots such as these should be infrequent, but may be necessary from time to time to apply upgrades that strengthen our security, reliability and operational performance.
There are two kinds of reboots that can be required as part of Amazon EC2 scheduled maintenance – instance reboots and system reboots. Instance reboots are reboots of your virtual instance, and are equivalent to an operating system reboot. System reboots require reboots of the underlying physical server hosting an instance. If you do not take any action, the impact on your instance is the same in both cases – during your scheduled maintenance window your instance will experience a reboot that in most cases takes a few minutes.
You also have the option to manage these reboots yourself at any time prior to the scheduled maintenance window. When you manage a reboot yourself, your instance will receive the upgrade when you reboot and your scheduled maintenance window will be cancelled (note that scheduled events can sometimes take up to 1 hour to refresh once a reboot has been completed).
Amazon EC2 Maintenance Help Page
We frequently upgrade our Amazon Elastic Compute Cloud (EC2) fleet, with many patches and upgrades being applied to instances transparently. However, some updates require a short instance reboot in order to apply these updates. This page provides information on the reboot process.
The recent release of our scheduled events functionality provides greater visibility into the timing of these reboots. In addition to added visibility, in most cases you can use the scheduled events to manage reboots on your own schedule if you want to reboot before the scheduled update window. You can easily view any upcoming scheduled events for your instances in the AWS Management Console or using the API tools or command line. Reboots such as these should be infrequent, but may be necessary from time to time to apply upgrades that strengthen our security, reliability and operational performance.
There are two kinds of reboots that can be required as part of Amazon EC2 scheduled maintenance – instance reboots and system reboots. Instance reboots are reboots of your virtual instance, and are equivalent to an operating system reboot. System reboots require reboots of the underlying physical server hosting an instance. If you do not take any action, the impact on your instance is the same in both cases – during your scheduled maintenance window your instance will experience a reboot that in most cases takes a few minutes.
You also have the option to manage these reboots yourself at any time prior to the scheduled maintenance window. When you manage a reboot yourself, your instance will receive the upgrade when you reboot and your scheduled maintenance window will be cancelled (note that scheduled events can sometimes take up to 1 hour to refresh once a reboot has been completed).
Hi Milan. Not true. unable to arm or disarm. Unable to sync rules...ticket raised yesterday.
Hi Milan. Not true. unable to arm or disarm. Unable to sync rules...ticket raised yesterday.
Hi Milan. This is urgent for me today. Needs to be treated high priority as I'm planning to visit potential customers (house developers) today evening and tomorrow to get some deals. If the system lets me down, it is possible customers will not be interested.
Please focus on my issue (especially the alarm part) with highest priority.
Thanks.
Hi Milan. This is urgent for me today. Needs to be treated high priority as I'm planning to visit potential customers (house developers) today evening and tomorrow to get some deals. If the system lets me down, it is possible customers will not be interested.
Please focus on my issue (especially the alarm part) with highest priority.
Thanks.
Replies have been locked on this page!