Alerts don't stop a service in time, usually go over before stopping

I have my account set to turn off data at 990MB so that it doesn't go over 1024 and into the next tier. However, this almost never works. For the current month, data stopped but not until they hit 1039. At that point, I'm going to get charged for the next tier and it's useless to turn it off. I would think if I set it to stop at 1023, it should stop at 1023, not let it keep going and going. Is this always going to be the case that the limits are just fuzzy lines?



1 comment
  • The limits are for sure hard limits, but it's REALLY important to note that we don't stop an active voice or data call with the network to install our cap.

    Using minutes as an example, if you're at 88 minutes with a minutes cap of 95 and place a 20-minute phone call, our cap will not apply until the call is complete, putting it in place at 108 minutes.

    The same goes for data calls. It's a little weird in how it works, but your phone creates a data "session" so-to-speak with the tower. For our purposes here, that's effectively a data call. If you're at 989MB for the month and your cap is at 990MB but you start a 45MB data session (easy to do, even in one app), our cap doesn't get put into place until that session is over at 1034MB.

    This is less noticeable when placing a cap for calls or texts, as calls tend to only be a few minutes a piece and text messages are a one-and-done kind of session thing. Data is tricker. The session tends to last for as long as your phone is actively requesting and sending data to the tower. 

    There are a few things you can do, though. You can set the buffer slightly lower if you feel like this is a regular thing that's going to happen. Or you can try to "force" your data sessions to complete by putting your phone into standby mode more often, though that's not a guarantee that an app isn't keeping the data session open in the background. Typically, you'd want to restrict the number of apps that have access to cellular data at all. This tends to be pretty easy on an iPhone.

    Keep in mind that we do have an unadvertised 5% buffer as well. Each bucket is technically 5% larger than advertised to cover just these kinds of occasions. You don't hit the next bucket up until you're 6% over the previous one, which we think is fair to assume is intentional that you'd want to be in that bucket, right?

    Comment actions Permalink

Please sign in to leave a comment.