Spark WISP Network
Wisp lets a web page open real internet connections through a WebSocket. Spark WISP Network is a small network of Wisp servers. It is not intended for public use: feel free to test or demo your configuration or project, but performance is deprioritized for purposes not approved ahead of time.
Connect
Point your Wisp client at this address. It reaches a server near you:
Keep the slash at the end of the address. To check a server, or debug your client, use the test page.
Limits
Limits apply per IP address, across all of your connections.
| Location | Speed | Connections | Streams per connection |
|---|---|---|---|
| Frankfurt, Kansas City | 12 Mbit/s | 16 | 128 |
| Tokyo, Singapore | 6 Mbit/s | 8 | 64 |
Apps that don't run in a browser are limited to 2 Mbit/s per connection. Servers can restart at any time, so your client should reconnect.
What you can't reach
- Private and local networks: only the public internet is reachable.
- Email sending (port 25) and Windows file sharing (ports 135, 139 and 445).
- IPv6 destinations: connections use IPv4 only.
Traffic leaves from shared addresses that some sites refuse, so a site may fail here and work elsewhere.
Acceptable use
By using this network you agree to these rules. Traffic leaves from shared addresses, so one person's abuse affects everyone.
Allowed
- Testing or demoing your own project, client or configuration.
- Learning how Wisp works.
- Anything else approved ahead of time.
Not allowed
- Attacking, flooding or scanning systems without permission.
- Spam, or other mass automated abuse.
- Malware, phishing, fraud, or anything illegal.
- Dodging the limits, or hiding the source of abuse.
- Reselling access, or running a production service on it without approval.
Access may be limited or removed at any time, with or without notice. The network is provided as is, with no guarantee of availability or speed, and you use it at your own risk.
Your data
- While you are connected, the server holds your IP address and the sites you connect to in memory, where its operator can see them.
- After you disconnect it keeps traffic totals per site without your address, and your address may remain for a while in a short list of recent disconnects.
- None of this is saved to disk, and all of it is cleared when the server restarts.
- Traffic passes through third-party networks. Anything you don't encrypt can be read in transit, so use HTTPS.