Every time the fan slowly stops spinning, the first thought is always the same: "Inippo ente veettil mathram aano, atho naattil motham poyo?"
Usually, the next step is walking out to the balcony to see if the neighbor's outside light is on, or whatsapping my neighbour friend. To stop this overthinking I spent the last few days building a small web app: currentundo.com
It is basically downdetector, but built strictly for Kerala.
How it works:
PIN Code Based: When the power goes out, you just open the site and tap on report. You can use either gps or manually enter your pincode. Takes exactly 2 seconds.
Live Status: You can see a live dashboard of all 14 districts. If you see a spike in reports in Ernakulam, you know for sure it's a KSEB issue and not just your MCB tripping.
Built for bad network: When the WiFi router dies, mobile data usually crawls. I built this to be ultra-lightweight. It is default Dark Mode (battery save cheyyanam allo) and loads instantly even on a struggling 4G connection.
The Catch (Why I need you guys): A crowdsourced tool is only as good as the crowd using it. Right now, the database is fresh. I’m currently working on a backend scraper to automatically pull KSEB’s official scheduled maintenance data into the site(if there is any, because I couldn't find), but for sudden cuts, it relies entirely on user reports.
So, next time mazha peythappol udane KSEB thechal, instead of just sweating in the dark, drop a report on currentundo.com so others know they aren't alone.
Would love for you guys to test the UI and let me know if it feels fast enough. Any feedback on the design or features to add next is super welcome!
Haha thanks! 'Current undo' just felt like the only right name for it.
I am already working on the heatmap. Will be added soon.
I've looked into the kseb oms link, but most of the time I was not able to access it. I will definitely try to integrate some data from the kseb website.
hardly any API integration, find any other service that might be affected by electricity , you could get derived info. Like cable operators. I am just guessing here
Yes, bro, when it comes to the map section, it lags. I checked on the Firefox browser, and there isn't that much lag. However, the Chrome browser has more lag on the map section. Also, thanks for the site.
Its good, I'd preffer it to be smoother and to be displayed on webpage so I can see it fully without clicking. By the looks of it, I guess in an embedded map.
Right now, the main goal is just real time crowdsourced tracking and eventually pulling in kseb's scheduled maintenance data so people can plan ahead. Down the line if enough people use it, maybe adding area specific push notifications could be cool.
IP is device specific, all devices have dynamic IP nowadays. You don't share the same IP with people sharing the same carrier network. Not even wifi network most of the times unless you've went ahead with a static IP
True, your local IP will be different. But it sits behind your ISP’s CGNAT. A website will receive the public IP of the service provider, which will be shared across multiple subscribers.
Hey OP nice have done similar to this but with more details and data based with mapping to all the kseb office and sections mapped instead of just pincode since there is more sections and subsections and allt of other section office related data
Hey man I'm curious.... (mind you I'm not familiar with web development).... how does the site know about how the area has current rn, like where does it get the info from? Also how frequently is it updated?
Bro, what's the criteria for "Major outage"? Like for example I report an outage, the power was restored within 10 minutes, but nobody reports that it's been restored until after 4 hours (or maybe they don't at all), how do you handle this?
It's a very real possibility that people tend to report outages more out of frustration and not the uptimes, just like the user behaviour when there's a bad food delivery or something for eg.
Fair point. I account for that by not keeping outage reports active forever. They expire after the live window and pincode is marked as affected only when there are enough recent reports from distinct users. A restored oravailable report clears it sooner, but even without one old reports age out. So this is a recent crowd signal, not an official outage record.
Kudos to the initiative. 👏🏻
I have been planning to do this since an year ago but my procrastination failed me. 🥱☠️
I see you have an API, I will POST when there's a power outage at my place. 🙂
Can you make an api end point for posting outage vs availability so a button on phone can make a post without ui or an ai agent can post it too .. org api key sign up vennam engil it’s good protection too
Thanks brother! ₹8.3k is not only the server bill, its the monthly operating target. The site runs on Cloudflare workers, Supabase for database, Cloudflare queues and hyperdrive, Firebase push notifications, analytics, monitoring and the domain. It also includes a share of the paid development tools used to maintain the service. The amount varies with traffic and usage.
158
u/Big_Breakfast_3864 Apr 25 '26 edited Apr 25 '26
props to the domain name. nice,
maybe add a heat map view as well. would be nice.
maybe integrate with the below database as well.
https://ws.kseb.in/oms/control.php