Summary

  • In February 2015, Nathalie Trenaman's RIPE NCC team found 460 members that had recently stopped announcing an IPv6 prefix. A later survey went to 462 LIR contacts and drew 69 responses plus direct email; those stages have different counts.
  • The RIPE NCC follow-up found several causes: a test ending, production IPv6 being withdrawn, and an operator unaware that its announcement had ceased. One lost star was not one diagnosis.

There is a peculiar comfort in awarding a star for a BGP announcement. The route is visible. The icon lights up. Nobody has to ask whether a customer can use IPv6 on Tuesday morning. RIPE NCC's IPv6 RIPEness programme counted an allocation, a route object, reverse DNS and a visible IPv6 announcement among its signals. The scheme made progress legible; its lost stars made retreat legible too, but only at first glance.

Trenaman was the RIPE NCC IPv6 Programme Manager when the team noticed 460 members whose IPv6 prefix announcement had recently disappeared. She presented the puzzle at RIPE 70, then asked operators what had happened. The subsequent survey reached 462 LIR contacts. Sixty-nine answered, with more writing directly. The two counts mark observation and outreach; they are not a denominator to be silently patched into one another.

Among respondents, 70% said the earlier announcement was a test before live use. Turning that route off could mean the rehearsal ended, not that a live service failed. More than 20% said they had already used IPv6 in production before switching it off, citing such reasons as restructuring, weak customer demand or security problems. Those are withdrawals with a different operational meaning. Trenaman also found operators who did not know the route had vanished. In one case, a member called its upstream; RIPEstat showed the upstream began announcing the prefix only after that contact. A scorecard had caught a missing route before its owner did.

The original RIPE NCC article reports that 40% of respondents could not say whether or when they would turn IPv6 on again, while a quarter expected to do so within weeks. Those are intentions from a small responding group, not a later measurement of recovery. A reader challenged the star system itself in the article's comments: an announcement can be obtained without an organisation committing to wide deployment. Trenaman replied that the anonymous survey might not reflect management's formal position. The distance between a route and a corporate decision had entered the room.

Her investigation did not turn every missing star into failure. It made the star answer a narrower, better question: is a particular signal visible now? To learn whether IPv6 is a durable service, someone must connect that signal to production use, monitoring and the decision to keep it running. The route table can tell you when the light goes out. Trenaman's follow-up asked who switched it off, and whether anyone noticed.