Summary

  • SANOG 34’s relocation was not one act by one visible institution. Sri Lankan hosts supplied security advice, an unnamed SANOG “we” announced the choice, Kolkata organizations rebuilt local delivery, and the programme committee controlled content.
  • The event’s July 31–August 7 window survived, relative to the April website, and APNIC reported more than 200 attendees. That result does not show that participation was unchanged, that every scheduled item occurred or that the move was costless.
  • Changed visa rules, registration dates, fellowship geography and programme order reveal the work hidden inside “continuity.” Missing minutes, contracts, matched registration data and a named legal principal prevent a stronger claim about formal power or consequences.

The unchanged dates that concealed a changed meeting

On July 31, 2019, SANOG 34 opened in Kolkata rather than Colombo. The event number was intact and the closing date remained August 7. The programme was recognizably SANOG’s: conference sessions, tutorials, five-day workshops, fellowships and an exchange of operating knowledge among people who build and run networks across South Asia.

That concise account leaves out most of the work.

To keep the outer dates, organizers replaced the venue, local host structure, registration interface, visa guidance, accommodation information and much of the public-facing machinery through which a conference becomes accessible. They changed the order of its component parts. They extended fellowship deadlines and shifted the geography of a local fellowship. A large sponsor roster appeared on the final event page. Meanwhile, the website migrated in stages, briefly displaying Kolkata alongside the old Colombo programme order. Continuity was the result of concentrated change, not its absence.

Crisis accounts often compress many different acts into one verb: an organization “moved” a meeting. The verb suggests a single actor exercising a settled power. SANOG 34’s public record instead separates at least five functions. The Sri Lankan local hosts advised on risk. An unnamed “we” on SANOG’s website said it took the decision. The Internet Society Kolkata Chapter and India Internet Foundation became the replacement host and co-host. The SANOG Programme Committee retained control over programme content. Sponsors supplied financial or in-kind support on disclosed tiers.

These functions worked together, but the record does not turn them into a legal hierarchy.

The most revealing document is not a resolution, contract or formal emergency rule. None has been made public in the located record. It is a sentence on an archived event page: “We took the decision on advise from the local host.” The source of advice is partly identifiable; the decision-maker is represented only by a pronoun. Local delivery then moved to a new group of institutions, while the programme remained in the hands of a committee whose published remit concerned content. The sentence exposes a working allocation of functions but cannot establish who formally held decision power.

SANOG 34 is worth examining for that tension. It is a positive story of delivery but an incomplete story of accountability. Its archive shows how a regional operators’ meeting continued through a severe security shock. It cannot show who signed, who paid, whether anyone lost money, who withdrew or who would have been liable had the replacement failed. A successful conference illuminates the operational surface. It does not fill the documentary gap beneath it.

Colombo was more than a name on a slide

The move is easy to misread if Colombo is treated as a loose aspiration. By January 2019, during SANOG 33, a presentation was already advertising the next meeting in Colombo for July 29–August 6. The SANOG 33 presentation discussed possible hotel and accommodation arrangements, network capacity, visa handling, airport transfers and local travel. It named Galle Face Hotel among the choices. It set out technical expectations associated with LEARN, the Lanka Education and Research Network: a 20 Gbps capacity figure, a 1 Gbps academic connection, 100 Mbps at the conference venue and 802.11n/ac Wi-Fi.

Those details are evidence of preparation, not proof of purchase. A bandwidth figure in a promotional deck does not show what was ultimately provisioned. A named hotel does not disclose a signed venue contract. Transport plans do not reveal paid bookings. The deck shows that detailed design work had been done; it does not permit a number to be attached to that work or a financial loss to be assigned when the city changed.

By April 19 and 20, the public plan was more specific and, in one important respect, different from January. The archived home page identified Galle Face Hotel, named LEARN as host and LKNOG as co-host, and showed July 31–August 7. The archived fellowship, registration, visa and programme pages made the event legible to prospective entities. Workshops were to come first, followed by conference and tutorial activity. Registration was expected to open on June 1. Sri Lanka’s electronic travel authorization was described as taking 24 to 48 hours, with LEARN serving as a contact for invitation support. The archived fellowship terms show that the application window had opened on April 15, with a May 16 deadline and a special local category for residents of Colombo and nearby cities.

The January and April date windows cannot be reconciled by ignoring either one. January said July 29–August 6. April said July 31–August 7. Later, when the relocation notice said there would be no change of dates, that claim was accurate relative to the April website immediately before the attacks. It was not a statement that the dates had never changed since the first advertisement. The difference is modest on a calendar but important in an accountability record: any claim of continuity needs a baseline.

The fellowship terms offer another glimpse of preparation without a balance sheet. The April page advertised transport support of up to $500 and a $300 full-registration obligation for fellows. Those are published entity terms, not proof of money already spent or a promise that every eligible expense was incurred. Public registration had not opened by April 20, and the final general fee schedule was not yet posted. That limits any claim that a broad pool of attendees had already paid. It does not rule out private bookings, organizer time, venue commitments, sponsor arrangements or travel plans.

The supportable conclusion is narrower: Colombo was an operational plan with multiple developed elements, while its contractual and financial state remains unknown.

Nor does the record establish that Galle Face Hotel was itself attacked or specifically threatened. The security shock was wider. On April 21, coordinated bombings struck churches and hotels in Sri Lanka, including sites in Colombo. The attacks came one day after the last located archive capture showing the Colombo event state. A later account can easily fuse the planned venue with the targets because both belong to the same city and hospitality landscape. The sources do not support that fusion.

The stated case for relocation rested on the broader security environment and local-host advice, not on evidence in this record of an attack at SANOG’s named venue.

A decision window bounded by archives

The days after April 21 brought severe, dated signals. Reuters reported on April 24 that tourists were cancelling Sri Lanka trips amid curfews and emergency conditions. On April 25, the United Kingdom advised against all but essential travel. That advice formally concerned British nationals, not every SANOG entity, but it could constrain people and employers using it as a risk reference. Within the same period, CITES postponed its much larger Colombo conference and ultimately moved it to Geneva. The CITES decision arose from a different institution, scale and set of obligations. It nevertheless shows that moving an international meeting was a reasonable response available in the circumstances; it says nothing about who made SANOG’s decision.

The public chronology is exact at its edges and indistinct in the middle. April 20 is the last located capture of the SANOG 34 home page in its Colombo state. By the May 13 fellowship capture, Kolkata appeared as the event city. The move in public state therefore occurred after April 20 and no later than May 13. The exact internal decision time is unknown. So is the exact first publication time. An archive captures pages when a crawler visits them, not every edit when it happens.

That distinction prevents false precision. The evidence does not support “the committee voted on May 2,” or any comparable sentence. No minutes, vote, quorum, resolution, emergency policy or risk matrix have been located. There is no public record of a formal local-host veto. There is no named person or constituted body behind the “we” that said it decided. The public interval may contain extensive deliberation, a rapid telephone agreement or several rounds of contingency work; the archive cannot choose among them.

What it can show is the decision as presented publicly. In the May relocation notice, SANOG said the choice was made on local-host advice with entity security in mind. It thanked LEARN and LKNOG for staying in contact and guiding organizers. It named the Internet Society Kolkata Chapter as host and India Internet Foundation—also rendered IIF or IIFON in the record—as co-host. It retained the July 31–August 7 window used on the April site.

The language gives LEARN and LKNOG consequential advisory influence, not a proved legal veto. It gives the unnamed regional organizers a visible role in decision and continuity coordination, without identifying SANOG’s legal identity in 2019, establishing a board or showing who could bind contracts. It gives Kolkata organizations a replacement-host execution role, without showing that either became SANOG or owned its regional brand. Those limits follow from what the announcement leaves unnamed; they should not be filled by inference.

The pronoun at the centre

Organizations built around recurring technical meetings can appear more institutionally complete than their records allow. A stable name, numbered events, chairs, committees, sponsors and a durable website create a coherent public identity. That identity can coordinate real work. It does not automatically answer legal questions.

The SANOG notice’s “we” is a case in point. It is evidence that regional organizers claimed the functional capacity to decide and preserve continuity. The event remained SANOG 34. Its number, brand, chair roles, fellowship machinery and programme process did not get replaced with a new Kolkata conference. Yet the pronoun is not a signature. The located sources do not say whether “we” meant a chair, a core group, a steering arrangement, a mailing-list consensus or some other body. They do not identify a contracting principal capable of holding a venue agreement or accepting liability.

This gap should not be filled with institutional imagination. SANOG’s 2019 legal identity is unknown in this record, as is the legal principal for Colombo or Kolkata contracting. The absence of a located document does not prove no such principal existed; it means the public archive being examined cannot name one. Similarly, no source identifies a vote, quorum, formal resolution, emergency trigger or appeal process. A reader can observe functional decision and continuity coordination without converting it into demonstrated legal power.

The allocation becomes clearer when compared with the programme committee. The final programme explicitly said track information and content could change according to the SANOG Programme Committee’s decision. That is strong evidence of programme control, not of a power to choose the city, assess entity safety, issue visas, sign venue contracts, control budgets or bear liability. A person associated with the original Sri Lankan host later described remaining involved in the programme process after the move. That continuity is consistent with the content role continuing even as local execution moved. It does not collapse host advice, regional decision and content curation into one power.

Ceremonial roles reinforce the separation. The final schedule distinguished local host representatives from SANOG Chair Rupesh Shrestha in welcomes and closing remarks. Such appearances show a shared event surface, not an agency contract. A person speaking for a host at the lectern does not thereby control SANOG’s programme. A chair closing the event does not thereby become the proved signatory to every hotel or sponsorship arrangement.

Sponsors occupy a fifth surface. The final footer lists an extensive set of host, co-host, supporting bodies, sponsor tiers, fellowship supporters, a social sponsor and a broadband partner. Those disclosures demonstrate resource mobilization. They leave contribution amounts, dates, conditions, the division between cash and in-kind support, continuity from Colombo, and any sponsor influence over relocation or programme undisclosed. Sponsorship may have made delivery possible. It is neither proof of capture nor proof of institutional independence.

The public record therefore shows local risk information, regional continuity coordination, local replacement execution, programme control and financial or in-kind support as distinguishable functions. That is a practical arrangement visible under pressure. Any formal arrangement relevant to the emergency does not appear in the located public record.

A website moving at human speed

The announcement presents one decision; the archived pages reveal implementation as a sequence. On May 13, the fellowship page already said Kolkata. On May 16, the programme page named Kolkata while still retaining the workshop-first order inherited from the Colombo plan. By the June 21 programme capture, the public programme had been reordered: conference on July 31 and August 1, tutorials on August 2, and workshops from August 3 to 7. A detailed schedule then appeared before the event.

The phased rewrite neither proves nor disproves competent management. It does show that the city label, programme architecture and detailed content changed on different timelines. The lags decompose “moving a meeting” into visible tasks. They also rule out describing the programme as unchanged.

The outer date window survived relative to April; the inner order did not. In Colombo’s April plan, workshops came first and conference/tutorial activity followed, with an apparent overlap on August 6 in the public schedule. In Kolkata’s final plan, two conference days came first, then a tutorial day with three parallel tracks, then three five-day workshops. That was more than a venue substitution. It could change when instructors, speakers and entities needed to arrive, how accommodation was used, how one component fed into another and which travel itineraries remained viable. Those effects were not measured.

Whether every final listed item happened exactly as scheduled is unknown. A final programme is a strong record of intended delivery and, together with the post-event reporting, supports the conclusion that the multi-part event ran. It is not a check-in log for every session. A published schedule should not be treated as a completed transcript.

Venue and local administration changed just as visibly. Galle Face Hotel gave way to Holiday Inn Kolkata Airport. The local registration contact moved from LEARN’s office to an ISOC Kolkata/SANOG secretariat interface. Accommodation and transport guidance were rewritten for the new city. These are ordinary logistics that a competent host must execute. They do not prove ownership of SANOG. They do show that continuity depended on a local organization capable of replacing multiple surfaces quickly.

A host-side Internet Society retrospective later said that the event was replanned and executed within four months. The description fits the public chronology and supports compressed execution. It comes from an organization connected to the replacement host and fellowship support, after a successful result. It is not an independent account of costs, rejected options or failed work. “Within four months” is useful as a host-side measure of tempo, not as proof that the replan was frictionless.

Access did not simply move with the venue

The most consequential changes for entities sit in pages that can look like administrative footnotes: visas, registration and fellowships. They show that geographic continuity and calendar continuity are not the same as access continuity.

Before the move, the site described Sri Lanka’s electronic travel authorization as taking 24 to 48 hours. After it, the Indian visa page set out a conference-visa process involving organizer letters and government clearances. It warned specified nationalities and people of Pakistani origin to allow 20 to 30 days. The page itself contains an institutional naming inconsistency, referring in one place to ISPAI even though ISOC Kolkata was the named host. That ambiguity is another reason to treat it as entity guidance rather than a complete institutional chart.

The numerical contrast—24 to 48 hours versus 20 to 30 days for specified cases—is stark, but it is not a universal before-and-after processing-time experiment. The Sri Lankan figure was general guidance, not measured approvals. The Indian warning applied to particular cases, not every attendee. No applications, approval timestamps, denials or withdrawals are available. The material finding is that the administrative regime changed and some entities were told to plan for much longer; the number delayed, deterred or otherwise affected cannot be counted.

The fellowship surface changed too. The April programme included a local category for Colombo and nearby cities. After relocation, that category shifted to Kolkata and nearby West Bengal. This is a straightforward geographic redistribution of local access: people who qualified because Colombo was local were no longer the intended nearby group, while Kolkata-area applicants became eligible. With no before-and-after applicant list, the net effect cannot be calculated.

Deadlines also moved. The original fellowship deadline was May 16. Archived revisions show that it was extended to May 24 and then May 28. Those extensions provided more time during a disrupted process. They say nothing by themselves about whether the extra days fully compensated applicants for the changed city, visa regime or travel requirements. The final records support 16 fellows. APNIC later reported an eight/eight gender split. That is a positive access result, not a matched comparison with a hypothetical Colombo cohort.

Registration moved in a different direction. The original page planned an opening on June 1 and named LEARN as the local contact. After relocation, registration opened on May 20 and local registration moved to Kolkata. On May 21, fees were still pending. By June 21, the public fee schedule showed $250 for a full passport, $150 for a workshop and $125 for tutorial/conference products, alongside smaller day products and INR equivalents. These are prices, not revenue. They do not reveal how many people paid each rate, whether any prior registration transferred, whether any refund was issued or which institution received funds.

No public record located for this account gives a Colombo applicant or registrant baseline. There is no count of cancellations, changed airline tickets, visa denials or people who decided not to travel. It is unknown whether speakers, instructors, fellows or sponsors withdrew because of the move. It is also unknown whether a sponsor, insurer, government, venue or employer compelled the decision. These omissions define what “successful relocation” can mean.

The final partial online-registration table illustrates the danger of answering a missing baseline with a convenient later number. Parsed as published, it contains 248 rows and 18 economy labels, including four rows labelled Sri Lanka and none labelled Pakistan. The table calls itself partial, contains duplicates and inconsistent fields, and is not a check-in ledger. Pakistan’s absence cannot be assigned to Indian visa rules. Demand, employer choices, bilateral conditions, organizer choices, data limitations or an unrecorded factor may explain it. Sri Lankan-labelled rows, meanwhile, refute any claim that relocation eliminated Sri Lankan participation, but they do not measure who could no longer attend.

Access was rebuilt, not simply transferred. The move exchanged one set of risks for another set of procedures. The available data establish those procedures, not their human incidence.

A substantial event, an incomplete measure of continuity

The event that emerged in Kolkata was substantial. The final published programme comprised two conference days, one tutorial day with three parallel tracks and three five-day workshop tracks. Its subjects ranged across Internet operations, routing security, disaster recovery and network resilience, DNS and DNSSEC, service-provider routing, facility design, containers, machine learning, Linux administration and security, and updates from network-operator communities. The breadth indicates category continuity: conference, tutorial and workshop functions all survived.

APNIC’s post-event report said more than 200 people attended from 15 economies. It reported 16 fellows, split evenly between men and women, and 25 entities in the Network Security workshop. APNIC supported and participated in the event, so the figures are partner-reported rather than independently audited. They remain meaningful outcome evidence: SANOG 34 was delivered at substantial scale, not merely relocated on a website.

The partial table’s 248 rows and 18 labels do not invalidate APNIC’s “more than 200 from 15 economies.” The two records describe different populations with different flaws. One is a partial online-registration table, not verified presence. The other is a post-event aggregate without a published underlying check-in dataset. Duplicate registrations, no-shows, late or offline entities and inconsistent economy labels can all create differences. Forcing the figures into agreement would produce false certainty; retaining both shows the measurement boundary.

The final public footer named the Internet Society Kolkata Chapter as host and India Internet Foundation as co-host. It also listed supporting bodies; GPX India as principal sponsor; APNIC and NIXI at diamond; Juniper and Telstra at platinum; Amazon, Facebook, Google, Sify and Tata Communications at gold; further silver and bronze sponsors; APNIC and Internet Society as fellowship supporters; and separate social and broadband support. That is evidence of substantial resource mobilization and of Kolkata’s ability to draw on a capable technical and commercial network.

The roster does not establish that sponsors selected Kolkata, approved the move or controlled the agenda. It leaves amounts, timing, conditions, continuity from Colombo and replacement costs undisclosed. A large sponsor network can help explain operational capacity without proving a particular governance design. It can also raise fair questions about dependence without answering whether there was capture. The public record shows support surfaces, not the communications or contracts behind them.

Kolkata’s existing operator-community capacity is a strong alternative explanation for success. A later Internet Society account linked hosting SANOG 34 to increased interest in the city’s community Internet exchange. That is a host-associated retrospective claim, not an independently quantified causal result. A cautious inference is that replacement execution required a network of people and institutions able to assemble venue, administration, connectivity, sponsorship and ceremonial functions quickly.

The event took place from July 31 to August 7. A two-day conference, tutorial day and workshops were publicly documented, and partner reporting described delivery. This supports operational continuity. It does not prove identical speakers, identical regional composition, zero entity harm, zero cost or flawless execution. There is no matched Colombo baseline against which the Kolkata outcome can be measured. “More than 200” tells us that a meeting happened at scale; it cannot tell us how many more might have attended in Colombo or how many different people came because Kolkata was now local.

What June hindsight can and cannot show

Crisis decisions are often judged with information that arrived after the choice. By June 25, Japan’s embassy in Sri Lanka announced that Japan had relaxed its nationwide advisory from level 2 to level 1, citing a more stable security situation after investigations and reinforcement. The easing came more than a month after Kolkata was visible on SANOG’s pages and only five weeks before the conference opened.

The later improvement is a real counter-test. It prevents a claim that conditions could only deteriorate or that relocation was objectively the sole possible response. Had SANOG retained Colombo, the meeting might have proceeded safely after security improved. That counterfactual cannot be verified. Risk tolerance also varies among entities, employers and governments.

But the June advisory cannot be carried backward into April. Organizers deciding between April 21 and May 13 faced immediate attacks, curfews, a state of emergency, severe travel advice and the example of another international conference leaving Colombo. A decision can be reasonable ex ante even if later conditions become more favorable. The absence of a public risk matrix means necessity is not proved; the dated context means the decision cannot fairly be dismissed as panic on the basis of later recovery.

A second reversal in late June would not have restored the untouched April plan. By then, Kolkata host arrangements, visa letters, registration, fellowship selections, sponsorship and programme reordering were in motion. Moving back might have imposed another planning shock on entities and hosts. No source gives the costs or practicability of that option, so it should not be assumed either impossible or easy. Reconsideration would have operated on a changed system, not the plan as it stood on April 20.

“Necessary” and “correct” are therefore poor final verdicts. The evidence supports “reasonable response under April–May conditions.” It does not support “only available option.” It supports a successful Kolkata delivery. It does not prove that the expected costs and risks of every alternative were compared under a disclosed rule.

Governance, or capable conference logistics?

There is a deflationary account of SANOG 34: conference organizers encountered an emergency, found another city and performed the logistical work. Venues, registration desks, visa letters, sponsors and programme edits are logistics, not proof of a governing structure. The extensive final sponsor roster and Kolkata’s established technical community may explain the outcome more directly than any regional design.

That account deserves substantial weight. Calling every logistical act an exercise of governing power would make the distinction useless. A hotel booking is not governance because it is difficult. A programme committee editing a track does not gain power over the host city because the work happens during a crisis.

What makes this case institutionally revealing is not the novelty of the tasks but their separation across actors. The local hosts had information and advisory influence rooted in exposure to Sri Lanka’s conditions. Whoever spoke through SANOG’s notice claimed enough functional coordination to announce a go/no-go choice and retain the SANOG identity. Kolkata institutions supplied host-execution capacity. The programme committee controlled content. Sponsors supplied resources. No single public document collapses those functions, and no public document supplies the legal chain behind them.

The disruption made this division visible because the default arrangement had to be replaced. In an ordinary year, the same people and logos might appear together on a footer, leaving the distinction between advice, decision, execution and support obscure. When the city changed, each function left a different trace: wording in the notice, replacement names in the footer, deadlines on fellowship pages, an altered visa process, a revised programme and a final outcome report.

The resulting arrangement appears capable of preserving a bounded regional function without publicly demonstrating a centralized legal apparatus. That can be useful: local groups can contribute risk knowledge and replacement capacity without waiting for an expansion of central institutions. It can also weaken accountability. When the actor behind “we” is unnamed and the principal behind contracts is invisible, entities cannot tell from the public record where a challenge, claim or request for reconsideration would go.

Ordinary competence and institutional design are not mutually exclusive explanations. Competence made the move work. Its distribution reveals the practical arrangement through which the work was done. Neither proves that the arrangement was formally authorized, equitable to every entity or financially benign.

The records success leaves behind—and the ones it does not

Public archives have a selection bias toward the plan that survived. The pages show Colombo before the attacks and Kolkata as the replacement became real. They preserve the successful programme, sponsor roster and entity-facing instructions. Private alternatives remain much less visible. Emails, calls, rejected cities, postponement scenarios, insurer discussions, employer restrictions, entity complaints and failed sponsor approaches may have materially shaped the decision.

Missing records must not be converted into proof of absence. Unlocated minutes do not prove there were no minutes; an unavailable public contract does not prove none existed; the lack of a public refund notice does not prove no refund was issued. The finding is simply that the public record cannot answer those questions.

The largest accountability gap concerns the legal and financial consequences of the decision. Who was the contracting principal for Galle Face Hotel, if a contract existed? Who contracted for Holiday Inn Kolkata Airport? Were deposits paid, cancellation charges imposed or insurance claims made? Did sponsors replace earlier commitments? Were entity payments transferred or returned? Who would have borne liability for a safety failure or a cancelled replacement event? None of these can be quantified or assigned from the sources here.

The same is true of entity consequences. There is no matched dataset linking Colombo applicants or registrations to Kolkata outcomes. Actual applications, visa denials, changed tickets and deterrence are unknown. Whether speakers, instructors, fellows or sponsors withdrew because of the move is unknown. The full before-and-after distribution by economy is unknown. The absence of a Pakistan label in a partial table has no established cause. The presence of four Sri Lanka-labelled rows confirms participation, not unchanged access.

Even the final programme has a boundary: it cannot establish that every scheduled session happened exactly as listed. Post-event reporting supports substantial delivery, but a complete session-level execution log is not public in this record.

These gaps do not erase the success. They explain why the outcome alone cannot audit the process. A crisis process should ideally disclose enough for entities to distinguish who advised, who decided, who executed and who accepted legal or financial consequences. SANOG 34 disclosed the first three functions unevenly and left the fourth largely invisible. It offered a reason—entity security—but no public threshold, formal decision rule, named approver or reconsideration mechanism.

Proportionate transparency need not mean publishing sensitive deliberations in real time. A post-event record could name the body that decided, describe the source and status of local advice, state the alternatives considered, identify the contracting or fiscal principal, explain whether entity payments and fellowships transferred, and report aggregate cancellations or visa problems without exposing individuals. Such a record would let future organizers learn from the event and entities understand who bore the consequences.

The lack of that record may reflect the norms of a technically focused conference community. It may instead reflect a structure whose operational capacity developed faster than its public accountability practices. The available evidence cannot decide between those explanations. It can show that a single unsigned pronoun carries more institutional weight in the surviving account than a reader should have to accept.

Conclusion: continuity needs a named subject

SANOG 34 did something difficult. After a severe April security shock, Sri Lankan hosts supplied advice rooted in local conditions. Regional organizers retained the meeting’s number, brand and functional continuity. Kolkata organizations rebuilt the local operating surface. The programme committee carried and reordered technical content. Sponsors and supporting bodies helped assemble the capacity to deliver. On July 31, the event opened; by August 7, a multi-part programme had run, with more than 200 attendees from 15 economies reported by APNIC and 16 fellows supported.

That outcome deserves to be called successful. It should not be called unchanged. The date window held relative to April, while the sequence, city, venue, visa regime, registration calendar, fellowship geography, host interface and sponsorship surface changed. Nor should the outcome be called harmless. The evidence has no matched baseline for the people who did not appear, no count of visa denials or changed journeys, and no financial record from which to calculate institutional or entity loss.

The late-June easing of Japanese travel advice does not invalidate a choice made under the information available weeks earlier, and it does not show that moving back was practical. It does show that relocation was a reasonable ex-ante response rather than a proven necessity or the only imaginable option.

The episode reveals a functioning division of labor under stress. Advisory influence, functional decision and continuity coordination, host execution, programme control and sponsor support were real and distinguishable. What remains hidden is equally important: the named decision-maker, the formal rule, the legal principal, the liability chain and the distribution of cost.

SANOG 34 does not show that an operators’ community needs a large bureaucracy before it can act. It suggests that a relatively thin regional arrangement can continue because local groups and technical committees carry different capabilities. But distributed action still requires legible accountability. A public sentence beginning “we took the decision” can move a meeting. After the emergency, it should be possible to say who “we” was, what function it exercised and where the consequences went.

Selected Sources

Editorial Metadata

  • SEO title: SANOG 34’s Colombo-to-Kolkata Move: Who Decided and Who Delivered
  • SEO description: How local risk advice, an unnamed SANOG decision, Kolkata host execution and programme control kept SANOG 34 running—and what the archive cannot reveal.
  • Focus keyword: SANOG 34 relocation
  • Slug: sanog-34-colombo-kolkata-crisis-decision
  • Open Graph title: Eight Days That Stayed Put: Inside the SANOG 34 Relocation
  • Open Graph description: SANOG 34 preserved its April date window by rebuilding its entity-facing machinery. The archive exposes distributed action and missing accountability.
  • Twitter title: What SANOG 34’s Move Revealed About Crisis Decisions
  • Twitter description: The Colombo-to-Kolkata record separates risk advice, decision, host execution, programme control and support—while leaving the legal principal unseen.
  • Featured image alt text: Editorial illustration of a conference schedule bridging maps of Colombo and Kolkata, with separate lines for advice, decision, hosting and programme control.
  • Featured image caption: SANOG 34 kept its April-published date window, but the move from Colombo to Kolkata required a new venue, host interface, visa process and programme order.
  • Image accessibility description: A non-photographic map composition places Colombo on the left and Kolkata on the right. Five labeled paths—risk advice, continuity decision, host execution, programme control and support—converge on the dates July 31 to August 7, 2019. No path is presented as a legal chain of command.
  • Featured image provenance: Original editorial illustration based on the dated public SANOG 34 archive and the geographic relationship between Colombo and Kolkata; it does not depict an undocumented meeting, individual decision-maker or contract.

Publication source register