myfl.uk · carrier register

Carrier status

Reported under RFC 1149 · no birds were used

Your connection, under the avian register

Entry loftCMH · Columbus
The Cloudflare data centre that answered this request.
Registered delivery loftBergen, Norway · the only route with documented service
Great-circle distance6,139 km
Payloadthis page
Departed the entry loft4 Aug 2026, 09:15:20 · server clock

Documented service figures

Observed 28 April 2001 in Bergen, Norway, by the Bergen Linux User Group with the Vesta Brevdueforening pigeon club. No later observations exist.

Date28 April 2001, Bergen
Packets transmitted9
Packets received4
Packet loss55%
Cause notedthe pigeons joined a neighbour's flock; two escaped without packets (the cage had been left open)
Ping interval7.5 minutes (ping -i 900)
Round-trip time, minimum3,211 s · about 54 min
Round-trip time, average5,223 s · about 87 min
Round-trip time, maximum6,389 s · about 106 min
Interface MTU (observed)150 bytes (tun0)
Nominal MTU (RFC 1149)256 milligrams
QoS classes (RFC 2549)Concorde, First, Business, Coach
Frequent flyer milesearned per packet; 50% bonus for Concorde and First
This routecoach

Route advice

Coach is the only class offered on this route. Ostriches (RFC 2549) give greater bulk transfer but slower delivery, and are not recommended for metropolitan service. Carriers carry an intrinsic collision avoidance system, which increases availability (RFC 1149).

Honesty

No bird carried this page. RFC 1149 and RFC 2549 are dated 1 April, and the protocol they describe has been implemented for real once, so far as the record shows: 28 April 2001 in Bergen, by the Bergen Linux User Group with the Vesta Brevdueforening pigeon club. The figures above come from that test and from the RFCs. The colo code, the distance and the clock time are real; the delivery method is not. The same network, reported honestly, is at /status.

The entry loft is read from the Cloudflare edge on this request. Nothing is stored. Back to the index.