Current Status ✅All systems go!
no news is good news
Previous Events of a Less Fortunate Nature
2021 December 25
The Filimin Manager (manager.filimin.com) and Filimin Remote functionality may have been temporarily unavailable due to high load.
2021 September 10 - 12
Our servers had issues this weekend that caused some lamps to be confused. The problem should now be resolved and any affected lamps should be back to normal!
2021 May 29 11.40am to 4:00pm CST:
Some lamps with older firmware lost connection and cried out in alarm. In the process of the resolving the situation your lamp may have rebooted, but all should be well and happy now!
CenturyLink, a global Internet provider, had a major outage that lasted most of the day. Multiple websites and servers across the world were affected and some Friendship Lamps were sad. Things should be all better now though.
2020 June 17-18, 10:00PM to 6:00AM CST: Server Provider Hardware Issues.
Our Filimin Manager web portal went down due to hardware issue with our service provider.
2020 May 6, 10:30AM to 1:00PM CST: Internal Issues.
The Filimin Manager and some internal tools were down for a few hours due to an internal error. Lamps continued to work fine during this time.
2019 June 27, midnight to 4AM CST: Service Provider Hardware Upgrades.
Our network service provider will be updating their hardware, causing "several minutes of packet loss." If your lamp's firmware is updated, you shouldn't notice anything except maybe a white flashing a few times as your lamp restarts itself looking to make a connection. Lamps with older firmware will pulse blue. All lamps may be unresponsive. If you are wondering if your lamp has old firmware, check out this article.
For about 10 minutes our web server was down for maintenance. While our website was down, most Filimins were unaffected.
2018 April 8, 5AM-5PM CST: Networking Issues.
Our service provider was experiencing networking issues. A few Filimins here and there might have had trouble seeing their friends. We didn’t witness any problems directly.
2018 April 6, 7pm-ish CST: Support email server misconfiguration.
Oops. We goofed and misconfigured our support email server, and we didn’t notice until April 7 in the morning. If you tried to contact us via our contact page the evening of April 6 or morning of April 7 and didn’t hear back from us, we might not have gotten the message. 🙁
2018 March 23, 1:30PM CST: 10 minutes of sadness and an afternoon of meh.
2/3 of the Filimins in the world lost connectivity for about 10 minutes. Poor things. Then, while not quite as severe, there were some coughs and wheezes from the network throughout the afternoon, causing a Filimin here and there to lose connection for a minute or two. But then the sun come out around 4pm CST and all is well again.
2018 March 12, 11am-noon CST: A few reboots due to server updates.
Two of our servers will be updated. Some of your Filimins might be taken a bit by surprise and reboot themselves, showing you a celebratory rainbow.
2018 March 6, 2:30-6:45pm CST: Meh? An occasional color display?
Our service provider reported that they were having intermittent issues that could affect connectivity. We did not see anything unusual in our nest but if your Filimin gave a holler and rebooted itself once or twice showing its celebratory colors during this period, that could have been the cause.
2018 March 5, 9:30-10pm CST outage: Blue pulsing and reboots. Website down.
Maintenance from our service provider triggered a complete outage of all Filimins. For about 1/2 of you, your Filimins rebooted and recovered quickly. For the other 1/2…well…we had some pretty upset Filimins for about 1/2 hour. A bunch of you crowded to our website to see what was going on, and this crashed our website. To address all of this, we moved our website to a much stronger server. We are also in communication with our service provider to better understand what happened and how to prevent this sort of outage in the future.
2018 February 26, 1-2pm CST intermittent outage: Blue pulsing and reboots.
To apply a security update, one of our central servers was rebooted by our service provider. Our secondary backup system did not kick in correctly, causing a temporary outage for some people.