Skip to content
shredstream.sh
Get a connection
Back
Reference

shredstream.sh service limits

Read every documented commercial, destination, verification, retention, wire, and regional limit without implied values for unspecified behavior.

How to read this page

Every known limit is stated as a concrete value. When the product facts do not fix a value, the table says “not currently specified.” That wording is deliberate. An absent contract must not become an invented number through repetition.

Commercial limits

LimitValueOperational meaning
Price$100One published price
Destinations included1One destination per purchase
Paid term30 daysCoverage per purchase
Maximum destinations per customer5A sixth destination is refused
Pricing tiersNoneOne plan is documented
Annual planNoneNo annual term is documented
TrialNoneNo trial is documented
Accepted payment assetsUSDC and SOLNo card path is documented
USDC conversion1:1USDC is taken at face value
SOL quote lifetimenot currently specifiedDo not assume a quote remains valid
Refund policynot currently specifiedNo refund behavior is defined in the product facts
Renewal lead timenot currently specifiedUse the displayed account timing

Destination and verification limits

LimitValueOperational meaning
Address changes per destination per day3Every change requires verification
Verification challenge lifetime600 secondsSubmit the current token inside this window
Challenge datagrams per request1One datagram is documented
Challenge resend countnot currently specifiedDo not automate against an assumed retry allowance
Challenge resend intervalnot currently specifiedNo pacing contract is documented
Destination IPv4 rangenot currently specifiedProduct facts do not state a numeric or CIDR policy
Destination UDP port rangenot currently specifiedProduct facts do not state minimum or maximum ports
Simultaneous old and new destination deliverynot currently specifiedDo not assume overlap during an address change
Delay from verification to streamingnot currently specifiedObserve actual packet arrival
Destination deletion recoverynot currently specifiedDo not assume a deleted destination can be restored

Expiration and retention limits

LimitValueOperational meaning
Expired verified-address retention90 daysAn unchanged late renewal avoids another challenge during retention
Stream delivery after term expirynot currently specifiedRetention does not state that streaming continues
State after 90 days expirednot currently specifiedDeletion, disabling, and recovery behavior are not defined
Grace period after expirynot currently specifiedDo not infer one from a late packet
Maximum inactive duration before cleanupnot currently specifiedNo separate cleanup duration is documented

Wire limits

LimitValueOperational meaning
TransportUDPDatagrams, not a connected byte stream
Maximum datagram size1,228 bytesReceive buffers must not be smaller
Mean packet size1,216 bytesMeasured value, not a per-packet promise
Ordered deliveryNoArrival order is not guaranteed
RetransmissionNoMissing datagrams are not resent by the wire contract
BackpressureNoA slow receiver does not slow the sender
Minimum datagram sizenot currently specifiedValidate the parsed variant
Fixed datagram sizenot currently specifiedUse the received length
Packet-rate capnot currently specifiedThe measured rate is not a limit
Bandwidth capnot currently specifiedThe measured rate is not a service ceiling
Burst-rate capnot currently specifiedSize and test receiver queues from observation
Duplicate-delivery boundnot currently specifiedDeduplicate by shred identity
Reordering boundnot currently specifiedDo not use a fixed window as a provider guarantee
Packet-loss service levelnot currently specifiedMeasure gaps and recover through FEC where possible

Source and region limits

LimitValueOperational meaning
Delivery regions1Only Frankfurt is documented
RegionFrankfurt, GermanyThe current delivery location
Documented source IPv4 addresses164.130.40.90
Additional source addressesnot currently specifiedAllow only the documented address
Source UDP portnot currently specifiedDo not pin a captured value
IPv6 deliverynot currently specifiedThe documented source is IPv4
Multi-region failovernot currently specifiedNo alternate region is documented
Customer-selected ingress regionnot currently specifiedNo region selector is documented

Measured operating point, not limits

MeasurementValueCaptured
Mean traffic rate54.3 Mbps2026-08-31
Mean packet rate5,585 packets per second2026-08-31
Mean packet size1,216 bytes2026-08-31
Projected monthly transfer at measured rate17.6 TB2026-08-31
Observation window5.6 hours2026-08-31

These figures describe one measured window. They are capacity-planning inputs, not minimums, maximums, service levels, or forecasts.

Service levels not fixed by the product facts

Service-level subjectLimit
Availabilitynot currently specified
Comparative latencynot currently specified
Absolute one-way latencynot currently specified
Support response timenot currently specified
Maintenance noticenot currently specified
Recovery timenot currently specified
Recovery pointnot currently specified
Data completenessnot currently specified
Slot coveragenot currently specified
Leader coveragenot currently specified

Questions

Is 5,585 packets per second a service limit?
No. It is the mean observed packet rate over a 5.6-hour measurement captured on 2026-08-31. The same distinction applies to 54.3 Mbps, the 1,216-byte mean, and 17.6 TB per month. None is documented as a minimum, maximum, service level, or future forecast.
How many destinations can one customer have?
One $100 purchase covers one destination for 30 days, and a customer can hold at most five destinations. Address changes are limited to three per destination per day, with verification required after every change. A sixth destination is outside the documented customer cap.
Why does this page repeat “not currently specified”?
The phrase marks a boundary in the product contract. It tells an operator that no safe numeric assumption exists for that row. A captured source port, observed burst, interface label, or one successful retry does not create a service guarantee and should not be copied into production policy.