Wink
moq.wink.co:4443/moq
A published MoQ endpoint on wink.co. Nothing is known about who runs it or on what.
What this is
- Operated by
- Wink
- Running
- Unknown Unverified. Nothing has been published about what runs at this address, and the probe has never completed a session with it that could report anything.
- Published URL
- https://moq.wink.co:4443/moq
- TestLab id
- wink
What TestLab measured
Not measured. This endpoint is in the TestLab fleet, and on 2026-09-14 the probe did not complete a session with it. There is no report.
A connection that does not complete says nothing about the relay behind it. The fault can as easily be ours, or the network's, and this project has already once published a failure of its own probe as a failure of somebody's relay. So this reads as no result rather than a bad one, and it will read that way until a session completes and produces something to report.
A published MoQ Transport endpoint on moq.wink.co.
Unknown is the answer here, not a gap. Nothing is known about who operates this endpoint or what runs on it. The operator name above is read off the hostname and nothing more: Wink registered wink.co, and that is the whole basis for it. No implementation is recorded because none has been published and none has been reported by the endpoint itself.
The registry keeps the row for exactly that reason. An endpoint we know nothing about gets the most conservative probing floor there is, and declining to guess is a position the record can hold — it is not the same as not having looked.
Is this your endpoint?
If something here is wrong, tell us — we keep what each result rests on, so a disputed one gets re-read rather than re-argued. We can also run this against endpoints that are not public.