The Mepa8 incident log is the public record of every vendor bill that surprised us, written up the way we wish the vendor had written it. Each entry carries the bill as we saw it, what was actually running, what we changed, and the one sentence an alert should have said days earlier.
We publish our own numbers for a plain reason. Mepa8 exists because three invoices in one month beat a team that reads logs for a living. Ryan Bolden and Nous went looking for a leak on 2026-10-07 and found three.
“We built it because the invoices kept winning.”Ryan Bolden, Mepa8, 2026-10-08
The three write-ups
The Neon bill that reached 93 dollars a month
A sync job rewrote every row of one table every 5 seconds. The compute never slept. 251 writes a minute, then 0.
Read the Neon post-mortemElevenLabs past its credit limit at 4.09M of 3.83M
One audio course rendered three times in September. 2.97M credits on batch text-to-speech, not the phone agents everyone blamed.
Read the ElevenLabs post-mortemRailway paused six projects on an expired trial
A bad card, an unpaid invoice, and CI red for 14 days. Main sat 321 hours ahead of production and nobody knew.
Read the Railway post-mortemHow to read an entry
Every incident follows the same five headings. What we saw is the bill or dashboard message, quoted. What was actually happening is the root cause with the numbers we measured, not the ones we assumed. What we changed gives the fix, the before and after, and the rollback. What a monitor should have said is the exact alert Mepa8 raises today for that condition. The lesson is one paragraph you can apply to a vendor we have never heard of.
Vendor rates on these pages link to the vendor's own pricing page, fetched the day the entry was written. Neon, for example, publishes its compute rate per CU-hour on neon.com/pricing, and that is the figure we multiply by our measured hours. Our own measurements sit in marked sections so you can tell a vendor's number from ours.
What counts as an incident here
Three things qualify. A charge more than 50% above the month's budget for that vendor. A vendor refusing service for a billing reason, as ElevenLabs did on 2026-09-13 when a past-due subscription stopped every phone agent. Or a platform pausing deployments, as Railway did on 2026-10-07. A slow drift of 10% does not make the log; the board handles that with a warning.
Entries are dated and carry a change log at the bottom. When a number changes because a vendor changed a price, the entry is updated and the change is noted, not silently rewritten.
Questions people ask
Why publish your own vendor bills?
Because the search that brought you here, something like why is my Neon bill 100 dollars, is the same search Ryan Bolden ran on 2026-10-07. A post-mortem with real numbers answers it faster than a feature page, and it shows what the monitor is for.
Are the numbers on these pages real?
Yes. Every figure comes from our own accounts: the Neon console, the ElevenLabs subscription API, the Railway dashboard and our own gate logs. Vendor list prices link to the vendor's pricing page on the day of writing, and our measurements are marked as first-hand.
Will more incidents be added?
Yes, whenever one of the three conditions above happens on an account we run. Mepa8 watches 21 vendors on our own board as of 2026-10-09, so the next entry is a matter of time, and that is the honest reason the product exists.
Sources
- Neon pricing — compute per CU-hour and storage per GB-month, fetched 2026-10-09
- ElevenLabs pricing — plan credits and the credit-per-character rule
- Railway pricing — trial credit, Hobby and Pro plans
Change log: October 9, 2026 — First published. Numbers are from our own accounts and logs.