The IEBC API hasn’t updated since sometime last night (10pm evening of March 5th, as best we can tell). They’ve gone to a completely manual system of counting the vote, which will be announced as they get updated.
A statement from the Commision clarifying ICT setup, issues and status would be appreciated in the vein of transparency at this critical time.
There are a lot of rumors swirling about a hack on the system. Reliable sources say this is not true, the system hasn’t been compromised.
Notes on how the tech system works (from someone working on it at Bomas):
- Next Technology is responsible for QA for the whole system from Safaricom to the VPN to the routing.
- RTS = results transmission system sends to servers physically located at Bomas
- Servers are owned and run by IEBC. Data is dumped into a file and then passed to Google for the API.
- JapakGIS is in charge of the visual web application - what you see at http://vote.iebc.or.ke/ (local firm on Thika road, owned by a past employee of ESRI)
Updated Flow of Information:
- Polling station uses Safaricom SIM cards »
- App installed in phone, proprietary software from IFES »
- Transmitted via Safaricom’s VPN »
- Servers hosted/managed by IEBC »
- JapakGIS runs the web layer, pulling from IEBC servers »
- Data file from IEBC servers sent to Google servers »
- Google hosted website at http://vote.iebc.or.ke »
- Google hosted API at http://api.iebc.or.ke
- Next Technologies is doing Q&A for the full system