The ATF's eForms system buckled on January 1, 2026, as 150,000 applications flooded in after the $0 tax stamp took effect. Users faced login errors, timeouts, and complete system crashes during the first 48 hours.

The ATF anticipated the surge and shut down eForms on December 26 to upgrade server capacity. It wasn't enough. The system rejected valid PINs on submission, pages wouldn't load, and authentication failures plagued users trying to submit their paperwork.

Why it matters: This represents the largest single-day volume in ATF history—a 5,900% increase over normal processing. Despite the chaos, some applications are moving through the system with approvals arriving in as little as 31 hours.

• The National Shooting Sports Foundation issued a bulletin on January 2 warning members: "ATF is experiencing intermittent IT system glitches and delays that are affecting industry members nationwide." The crashes affected login authentication, PIN validation, page loading, and caused complete system outages throughout the first two days.

By the numbers: The scale of this surge is unprecedented.

• 150,000 applications on day one
• 2,500 applications on a normal day
• 31 hours for the fastest reported approval
• 3-7 million projected applications for all of 2026

"ATF is experiencing intermittent IT system glitches and delays that are affecting industry members nationwide."
— National Shooting Sports Foundation bulletin

The system is showing signs of recovery as server loads stabilize. Users who successfully submitted applications during the initial chaos are beginning to see movement on their paperwork, though processing times remain unpredictable.

The bottom line: The system broke under historic demand but is stabilizing. Check your submission status if you got through—expect continued delays if you're still trying to submit.

Go deeper:

• Pew Pew Tactical
• TTAG

Read the original article in The Handbook | By Steve Duskett

Join the Discussion

Were you one of the folks trying to file that first day, or are you waiting to see if the site stabilizes before jumping in with your application?