Pause, Resume or Delete a Session: What Happens to Your Bandwidth
Pausing, releasing and deleting all look like ways to stop a session spending bandwidth, but they do different things to your GB and to your credentials. Picking the wrong one is how people end up with an endpoint they deleted by mistake, or bandwidth they thought they had recovered that is still sitting on a paused session. This guide explains each one precisely.
| Pause | Release unused GB | Delete | |
|---|---|---|---|
| Connections | Stop working | Keep working | Stop working for good |
| Credentials and settings | Kept | Kept | Removed |
| GB on the session | Stay on the session | Unused GB go back to your balance | Unused GB go back to your balance |
| GB already used | Stay counted | Stay on the session | Not refunded; kept in your usage totals |
| Can be undone | Yes, with Resume session | Yes, by topping the session up again | No |
Pausing a session
Pause is for stopping traffic without losing anything. Open an active session and choose Pause at the bottom of the card. You will see "Session paused — it won't use bandwidth until you resume it". The session keeps its allocation, credentials and settings, but it will not connect until you resume it.
- →Only an active session can be paused. A session that is still queued cannot.
- →Pausing does not return any GB to your balance. The unused GB stay allocated to the paused session. If you want them back, you need to release or delete (see below), and a paused session has to be resumed first because its tabs are hidden while it is paused.
- →Auto-allocate does not top up a paused session. It only acts on active ones.
- →Pausing a session that is already paused does nothing harmful, so a repeated click or a retry after a timeout is safe.
What a paused session looks like
In your list, a paused session carries a SUSPENDED badge, and the Suspended filter appears once you have at least one. That label does not mean anything has gone wrong. Open the session and read the banner, which says who stopped it:
| Banner says | Who did it | Can you undo it? |
|---|---|---|
| You paused this session. It keeps its bandwidth and settings but won't connect until you resume it. | You | Yes. Choose Resume session. |
| This session is paused because your account is suspended. | Your account was suspended | It comes back when the account is reinstated. Nothing is lost. |
| This session was disabled by our team. | GlobProxy | No. Contact support from the banner. Your bandwidth is safe and nothing has been deducted. |
Resuming a session
Choose Resume session on the banner. You will see "Session resumed" and the session is live again with its full allocation and the same credentials, so nothing needs to be re-copied. Only a pause you made yourself can be resumed from your dashboard.
An account can have at most 100 live sessions, counting active and queued ones. Paused sessions do not count, but resuming one adds it back. If you are already at 100, the resume is refused with "You already have 100 live sessions, so this one can't be resumed. Delete an unused session first, then resume it." Delete a session you no longer need, then resume.
Deleting a session
Delete is permanent. Choose Delete session at the bottom of the card, then Confirm delete. The button disarms itself after a few seconds, so a stray click later cannot delete anything. For sensitive actions you may also be asked to confirm with your password or authenticator code.
- →Unused GB return to your balance. The success message says how many, for example "Session deleted — 3.4 GB returned to your balance".
- →GB the session already used are not refunded. They stay counted in your account's usage totals, so your history still adds up after the session is gone.
- →Credentials stop working at once, and any named sticky sessions inside it are deleted too.
- →It works on a paused session and on one that is still queued. For a queued session, the GB reserved for it come straight back.
- →A session a reseller allocated to you cannot be deleted by you. Contact them.
If all you want is some of the unused GB back, deleting is the wrong tool, because it also removes the endpoint. Use Release unused GB on the Bandwidth tab instead. If you want a copy of the settings before you delete, press Duplicate first.
Doing it for many sessions at once
- 1In My Proxies, tick the checkbox on each session, or choose Select all shown to take everything matching your current search and filter.
- 2A bar appears with Pause, Resume, Add GB, Change country and Delete. The counts on Pause and Resume show how many of your selection each action applies to, since only active sessions can be paused and only ones you paused can be resumed.
- 3Confirm in the dialog. Delete tells you roughly how much unused bandwidth will return and that it cannot be undone.
Selections larger than 20 are handled in batches of 20, and each session is handled independently. If a few fail, you get a message naming them and they stay selected so you can retry exactly those. Sessions hidden by your current filter are never touched.
Which one should I use?
| If you want to | Use |
|---|---|
| Stop a job from spending bandwidth for a while, and come back to the same endpoint | Pause |
| Get some unused GB back and keep the session running | Release unused GB |
| Get all unused GB back and discard the session and its credentials | Delete session |
| Stop a leaked password from being used | Rotate password on the Credentials tab. Pausing also stops traffic, but only rotation changes the secret. |
| Make room under the 100-session limit | Delete sessions you no longer need |
Pause can be undone in one click and loses nothing. Delete cannot be undone. When you are unsure whether you still need an endpoint, pause it, and delete it later once you are certain.
Frequently asked
Still stuck?
Email us at support@globproxy.com and include your account email and what you see on screen.
Contact support →