LoTek Coordination

Network health

61 of 64 networks operational

Every network, with 90 days of daily history. Each node is polled every five minutes; this summary is as of Nov 2, 2026, 06:00 UTC.

Right now

Nodes online
3,624 of 3,690
Average uptime, 90 days
99.95%
This site
99.99% over 90 days

  • Degraded Grainline, Buffalo · since 2026-11-02 02:15 UTC

    Lake-effect snow

    Heavy lake-effect snow overnight. Four rooftop nodes are offline and two links are degraded while dishes are iced over. Stewards will clear them after sunrise.

  • Maintenance Fordline, Detroit · since 2026-11-02 05:00 UTC

    Scheduled hub replacement

    Planned overnight replacement of a Gantry H3 hub with an H5, midnight to 4:00 am local time. Rooftops served by the hub have been moved to neighboring hubs for the window.

  • Degraded Las Mareas, San Juan · since 2026-11-01 21:40 UTC

    Grid outage

    A grid outage since yesterday evening has left nine rooftop nodes without power. Hubs are running on solar and battery as designed, and the backbone is up.

Ninety days

OperationalDegradedMaintenance

Recent incidents

Everything that degraded a network in the last 90 days, newest first. Routine firmware rollouts are recorded in each network’s maintenance log.

  1. · Gilpin Row, Richmond · Resolved

    Power cut

    The rooftop nodes on the affected blocks went down with the grid. Hubs stayed up on battery.

    Degraded service · 4 hours 27 minutes · about 6 of 29 nodes affected

  2. · Tannery Row, Milwaukee · Resolved

    Planned backhaul work

    Done overnight. Members were told a week ahead at the monthly assembly.

    Planned maintenance · 2 hours 31 minutes · about 4 of 48 nodes affected

  3. · Lindenvale, Pittsburgh · Resolved

    Upstream outage

    The network’s transit provider had an outage of its own. The mesh itself stayed up, and local services kept working.

    Degraded service · 55 minutes · about 79 of 84 nodes affected

  4. · Ashgrove, Chester · Resolved

    Power cut

    The rooftop nodes on the affected blocks went down with the grid. Hubs stayed up on battery.

    Degraded service · 1 hour 57 minutes · about 8 of 95 nodes affected

  5. · Sedgley Hollow, Philadelphia · Resolved

    Upstream outage

    The network’s transit provider had an outage of its own. The mesh itself stayed up, and local services kept working.

    Degraded service · 1 hour 27 minutes · about 46 of 49 nodes affected

  6. · Apollo Square, Baltimore · Resolved

    Power cut

    The rooftop nodes on the affected blocks went down with the grid. Hubs stayed up on battery.

    Degraded service · 3 hours 25 minutes · about 9 of 89 nodes affected

  7. · Southgate, Bridgeport · Resolved

    Backhaul fiber cut

    A construction crew dug through the fiber. Traffic moved to the backup link at reduced speed until the provider spliced the cable.

    Degraded service · 2 hours 13 minutes · about 20 of 88 nodes affected

  8. · Fordline, Detroit · Resolved

    Upstream outage

    The network’s transit provider had an outage of its own. The mesh itself stayed up, and local services kept working.

    Degraded service · 46 minutes · about 60 of 62 nodes affected

  9. · Levee Ward, New Orleans · Resolved

    Upstream outage

    The network’s transit provider had an outage of its own. The mesh itself stayed up, and local services kept working.

    Degraded service · 1 hour 25 minutes · about 40 of 43 nodes affected

  10. · Tug Fork Hollow, Welch · Resolved

    Power cut

    The rooftop nodes on the affected blocks went down with the grid. Hubs stayed up on battery.

    Degraded service · 2 hours 16 minutes · about 3 of 23 nodes affected

  11. · Las Mareas, San Juan · Resolved

    Backhaul fiber cut

    A construction crew dug through the fiber. Traffic moved to the backup link at reduced speed until the provider spliced the cable.

    Degraded service · 3 hours 57 minutes · about 37 of 89 nodes affected

  12. · Millrace, Providence · Resolved

    Storm damage

    High winds knocked several dishes out of alignment. Stewards realigned them once it was safe to go up.

    Degraded service · 18 hours 42 minutes · about 4 of 60 nodes affected

  13. · Coahoma Crossing, Clarksdale · Resolved

    Storm damage

    High winds knocked several dishes out of alignment. Stewards realigned them once it was safe to go up.

    Degraded service · 8 hours 32 minutes · about 3 of 25 nodes affected

  14. · Port Row, Elizabeth · Resolved

    Planned backhaul work

    Done overnight. Members were told a week ahead at the monthly assembly.

    Planned maintenance · 2 hours 55 minutes · about 7 of 56 nodes affected

  15. · Ashland Park, East Orange · Resolved

    Backhaul fiber cut

    A construction crew dug through the fiber. Traffic moved to the backup link at reduced speed until the provider spliced the cable.

    Degraded service · 7 hours 48 minutes · about 62 of 146 nodes affected

  16. · Chatham Ridge, Savannah · Resolved

    Planned backhaul work

    Done overnight. Members were told a week ahead at the monthly assembly.

    Planned maintenance · 1 hour 33 minutes · about 3 of 42 nodes affected

  17. · Ashgrove, Chester · Resolved

    Upstream outage

    The network’s transit provider had an outage of its own. The mesh itself stayed up, and local services kept working.

    Degraded service · 1 hour 24 minutes · about 91 of 95 nodes affected

  18. · Rancho Coronado, Fresno · Resolved

    Planned backhaul work

    Done overnight. Members were told a week ahead at the monthly assembly.

    Planned maintenance · 3 hours 39 minutes · about 5 of 39 nodes affected

  19. · Tidewater Heights, Jersey City · Resolved

    Planned backhaul work

    Done overnight. Members were told a week ahead at the monthly assembly.

    Planned maintenance · 2 hours 58 minutes · about 6 of 48 nodes affected

  20. · Lindenvale, Pittsburgh · Resolved

    Power cut

    The rooftop nodes on the affected blocks went down with the grid. Hubs stayed up on battery.

    Degraded service · 2 hours 8 minutes · about 8 of 84 nodes affected

  21. · Highbanks, Louisville · Resolved

    Backhaul fiber cut

    A construction crew dug through the fiber. Traffic moved to the backup link at reduced speed until the provider spliced the cable.

    Degraded service · 2 hours 40 minutes · about 8 of 39 nodes affected

  22. · Arbor Row, Indianapolis · Resolved

    Upstream outage

    The network’s transit provider had an outage of its own. The mesh itself stayed up, and local services kept working.

    Degraded service · 59 minutes · about 57 of 61 nodes affected

  23. · Marquette Flats, Toledo · Resolved

    Planned backhaul work

    Done overnight. Members were told a week ahead at the monthly assembly.

    Planned maintenance · 1 hour 56 minutes · about 6 of 48 nodes affected

  24. · Bayshore Flats, Stockton · Resolved

    Power cut

    The rooftop nodes on the affected blocks went down with the grid. Hubs stayed up on battery.

    Degraded service · 3 hours 8 minutes · about 5 of 30 nodes affected

  25. · Fordline, Detroit · Resolved

    Storm damage

    High winds knocked several dishes out of alignment. Stewards realigned them once it was safe to go up.

    Degraded service · 14 hours 4 minutes · about 3 of 62 nodes affected

  26. · Santa Cruz Bend, Tucson · Resolved

    Planned backhaul work

    Done overnight. Members were told a week ahead at the monthly assembly.

    Planned maintenance · 1 hour 34 minutes · about 5 of 36 nodes affected

  27. · Bridgeside, Newark · Resolved

    Backhaul fiber cut

    A construction crew dug through the fiber. Traffic moved to the backup link at reduced speed until the provider spliced the cable.

    Degraded service · 7 hours 16 minutes · about 22 of 81 nodes affected

  28. · Steelmark, Gary · Resolved

    Backhaul fiber cut

    A construction crew dug through the fiber. Traffic moved to the backup link at reduced speed until the provider spliced the cable.

    Degraded service · 2 hours 12 minutes · about 16 of 64 nodes affected

  29. · Elm Hollow, Irvington · Resolved

    Backhaul fiber cut

    A construction crew dug through the fiber. Traffic moved to the backup link at reduced speed until the provider spliced the cable.

    Degraded service · 6 hours 19 minutes · about 29 of 59 nodes affected

  30. · Ferrywood, Norfolk · Resolved

    Upstream outage

    The network’s transit provider had an outage of its own. The mesh itself stayed up, and local services kept working.

    Degraded service · 1 hour 13 minutes · about 42 of 46 nodes affected

  31. · Canal Row, Newark · Resolved

    Storm damage

    High winds knocked several dishes out of alignment. Stewards realigned them once it was safe to go up.

    Degraded service · 14 hours 38 minutes · about 3 of 67 nodes affected

  32. · Ironwood, Birmingham · Resolved

    Planned backhaul work

    Done overnight. Members were told a week ahead at the monthly assembly.

    Planned maintenance · 3 hours 48 minutes · about 4 of 53 nodes affected

  33. · Bayshore Flats, Stockton · Resolved

    Planned backhaul work

    Done overnight. Members were told a week ahead at the monthly assembly.

    Planned maintenance · 3 hours 15 minutes · about 2 of 30 nodes affected

  34. · Gravois Bend, St. Louis · Resolved

    Storm damage

    High winds knocked several dishes out of alignment. Stewards realigned them once it was safe to go up.

    Degraded service · 4 hours 35 minutes · about 3 of 49 nodes affected

  35. · Westcroft, Cincinnati · Resolved

    Storm damage

    High winds knocked several dishes out of alignment. Stewards realigned them once it was safe to go up.

    Degraded service · 9 hours 5 minutes · about 2 of 55 nodes affected

  36. · Sedgley Hollow, Philadelphia · Resolved

    Upstream outage

    The network’s transit provider had an outage of its own. The mesh itself stayed up, and local services kept working.

    Degraded service · 1 hour 29 minutes · about 48 of 49 nodes affected

  37. · Oakbend, Hartford · Resolved

    Power cut

    The rooftop nodes on the affected blocks went down with the grid. Hubs stayed up on battery.

    Degraded service · 3 hours 35 minutes · about 14 of 68 nodes affected

  38. · Market Bend, Wilmington · Resolved

    Storm damage

    High winds knocked several dishes out of alignment. Stewards realigned them once it was safe to go up.

    Degraded service · 12 hours 12 minutes · about 9 of 102 nodes affected

  39. · Blue Bend, Kansas City · Resolved

    Upstream outage

    The network’s transit provider had an outage of its own. The mesh itself stayed up, and local services kept working.

    Degraded service · 33 minutes · about 29 of 32 nodes affected

  40. · Hunts Ridge, Bronx · Resolved

    Upstream outage

    The network’s transit provider had an outage of its own. The mesh itself stayed up, and local services kept working.

    Degraded service · 1 hour 26 minutes · about every node affected

  41. · Río Bajo, El Paso · Resolved

    Backhaul fiber cut

    A construction crew dug through the fiber. Traffic moved to the backup link at reduced speed until the provider spliced the cable.

    Degraded service · 7 hours 41 minutes · about 12 of 50 nodes affected