Mozilla site down due to "overdue hosting payments" [fixed]

Original Article ↗ Hacker News Discussion ↗

Cause of the Incident

  • The affected site is Mozilla’s Discourse forum, not mozilla.org; it was put into read-only mode with a system message about overdue hosting payments.
  • A Mozilla representative explains it was a delayed migration from self-hosted to hosted Discourse; the transfer was initiated late, and Discourse’s automatic non-payment safeguard triggered.
  • The issue has since been fixed, but some commenters still add it to a broader list of recent Mozilla missteps.

Responsibility for Payments & Ops

  • One view: ops/devops should rigorously track bills, certificates, secrets, etc., and this is a simple oversight.
  • Counterpoint: in a mature organization, SaaS bills belong to finance/business operations, not engineers; modern recurring billing should prevent this.
  • Others note that getting large organizations to pay small vendors on time is often a nightmare, even without malice.

SaaS Suspension and Public Messaging

  • Debate over Discourse publicly stating non-payment:
    • Some see it as an effective, fair pressure tactic and transparency for end users.
    • Others call it unprofessional “public shaming,” especially for high-profile B2B customers or in cases of billing errors/disputes.
  • Several suggest multiple automated reminders and possibly personal outreach before suspension; others argue delinquent or disorganized customers aren’t worth extra effort.

Perceptions of Mozilla & Firefox

  • Some suspect the timing (amid ToS/“selling data” controversy) is not accidental and reflects deeper financial or governance problems; others say this is likely just an oversight and warn against overinterpreting.
  • Disagreement over Mozilla’s financial health: one side claims it’s heading toward bankruptcy; another points to large cash and investments, while warning about overreliance on Google search revenue.
  • Longtime users express declining trust: frustration with perceived “cash frittering,” product bloat, and ToS wording, but many still see Firefox as the best non-Chromium, strong-adblocking option.
  • Side debate on Manifest V2 vs V3: some value V2 for powerful blockers like uBlock/NoScript; others prefer V3’s finer-grained extension permissions despite limitations.

Discourse Platform & UX

  • Some are satisfied with Discourse performance; others complain it’s slow and dislike it hijacking browser “find in page” shortcuts.
  • Suggestions that browsers should mediate keyboard shortcut overrides and prompt users before allowing web apps to capture them.

Late Payments & Process Lessons

  • Many share experiences of chronic late payments from large enterprises (auto, telco, etc.) and bureaucratic approval chains causing missed NET30 deadlines.
  • Opinions split between “a one-off oversight happens to everyone” and “late or chaotic payers aren’t worth keeping.”
  • Process recommendations:
    • Use shared billing email addresses (e.g., ap@…) monitored by multiple people.
    • Avoid tying critical billing and vendor communication to a single employee’s mailbox.
  • One commenter muses about a service to crowdshare data on chronic late-payer companies, funded via selling that intelligence to insurers.