Key Takeaways
- laravel sms gateway how to load test carefully is staff canaries and radio pace — not a tool to dodge carrier filters.
- More PHP-FPM workers only accelerate failure if one SIM is the bottleneck.
- Raise OEM/Android SMS rate ceilings as an ops setting. Carrier fair-use still applies. This is not unlimited carrier send.
- Do not point k6 at production OTP. Pin login codes on another deviceId.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Soak SMS still spend operator airtime.
- Free is 300 lifetime — not a city soak.
Canaries, not filter evasion
Search intent for laravel sms gateway how to load test carefully is whether Horizon can enqueue faster than a handset can send — not how to sneak past operator filters. Service pricing is based on device count and total SMS sent through the gateway. Hub: Laravel SMS gateway. CTIA messaging principles are a floor for promo programs (CTIA messaging principles), not a bypass cookbook.
If the test plan says “until it stops looking like spam,” stop. That is not a load test. That is an abuse test we will not run.
What you are actually measuring
Queue wait, last-seen, DLR fail rate, operator throttle. Not “inbox guaranteed.” Real handsets.
| Test | OK | Not OK |
|---|---|---|
| Queue depth | Horizon jobs wait; radio paced | Uncapped dispatch until 429 forever |
| OEM ceiling | Documented messages/min on that phone | “Remove Android SMS rate limits” as if carriers vanish |
| Destinations | Staff / lab SIMs you own | Customer lists or purchased dumps |
| Copy | Same templates you will ship | Gibberish to “bypass spam filters” |
OEM ceilings still apply
You can raise Android/OEM SMS rate ceilings as a device setting. Carrier fair-use and plan caps still apply. Starter, Professional, and Business list Unlimited SMS as platform send volume; that is not unmetered carrier SMS. Kotlin bulk loop. Priced by devices and SMS send volume. You use your own phone and operator SMS credit.
Horizon workers ≠ extra SIMs
Scale devices when you need throughput. Multi-device. Docs: docs.sms-gateway.app.
Never soak the OTP radio
Pin login. Laravel OTP. Pause the soak if last-seen goes stale.
Careful load-test checklist
- Written cap: messages/min and duration.
- Staff destinations only.
- OTP device idle / isolated.
- Idempotency-Key on every job.
- Stop rule: DLR fail spike or last-seen gap.
Next steps
Canary, then a short paced soak, then stop. Pricing. Train support.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS API documentationLive endpoint reference
- PHP REST send samplesPHP code examples
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
