
Tell us what broke and we will go and check it
A code that failed at the checkout is the most useful thing you can send, because it is the one thing we cannot see from here. Pick the route that fits, and include enough for the problem to be reproduced. Last updated 3 September 2026.
Three things this form is for
Each route asks for the detail that makes the problem answerable without a second email.
A code did not work
Send the provider, the exact code, and what the checkout said when it refused. That last part is what makes it quick to reproduce, and it is the part most reports leave out.
Report a dead codeSomething on a page is wrong
Send the page address and the sentence you are disputing. Corrections are made on the page itself rather than buried in a changelog.
Send a correctionYou are a provider
Offer changes, eligibility wording, a takedown of a withdrawn code, or a partnership question. Naming the code or the page saves a round trip.
Provider and partnershipThere is a fourth route on the form itself for privacy and data requests, which is the one the privacy policy points at. It is not a card here because it is a different kind of request, not a correction.
One form, four routes
Only the email and the message are required. Everything else makes the answer faster.
And what not to put in the box
- The provider name and the exact code, spelling included
- What the checkout actually said, quoted if you can
- The page address you were looking at
- The country or plan you were buying, when the code is region limited
- Payment card details. Nothing on this site needs them
- Passwords, or the login for a provider account
- An eSIM QR code or activation code. Those are worth money and are single use
- Passports or identity documents, even if a provider asked you for one
A confirmed dead code is marked as no longer applying, with the date and the reason the checkout gave. It is not deleted, because the next reader needs to know it was already tried. The method page describes that process in full.
This page should say how quickly a message is acknowledged, and right now it does not, because no commitment has been made. Pick a number you can hold to even in a bad week. It is better to publish three working days and meet it than twenty four hours and miss it.
Messages currently go to the WordPress administrator address, which is on a different domain from this site. A published address at esim.qpon, and a separate one for privacy requests, would let people reach you without the form and would look far less anonymous to anyone assessing the site.
Before you write
How fast will you reply?
Will you remove a code if I report it?
My eSIM will not connect. Can you fix it?
Do I have to give my name?
I am a provider and a code here is wrong.
Last updated 3 September 2026. Related: About, How we review deals, Affiliate disclosure, Privacy policy, Terms of use.
Now go and use one.
Most messages here start with a code that stopped working. Check the current list first.
