Summary

  • In an NPIX notice dated 5 April 2026, CEO Rupesh Shrestha said local exchange traffic had crossed 100 Gbps. Earlier spikes had happened; this time the level looked more consistent to him.
  • NPIX describes more than 40 peering members at two locations. The durable test is whether those independent networks keep exchanging local traffic through the exchange, beyond the day a graph makes a pretty headline.

A traffic graph can throw a party for one minute and send everyone home before the cake arrives. Rupesh Shrestha had seen NPIX touch 100 Gbps in earlier spikes. In his 5 April 2026 note on the exchange’s own site, he chose a more telling word for the new crossing: consistent. The local traffic rate was coming back often enough to look less like a stunt and more like ordinary work.

Shrestha is NPIX’s CEO, identified as such in his APNIC nominee statement. The exchange gives networks a local place to meet. They still choose to connect, announce routes, set policies and send traffic. The NPIX description of its footprint lists more than 40 members at two locations and says it serves more than 15 million Internet users. Those are the exchange’s current operating figures. Its April announcement gives a traffic rate, not a count of users moving 100 Gbps at once. The units matter because a peering platform is judged at packet speed, while the number of people served describes reach.

Why did Shrestha bother mentioning earlier spikes? One burst can come from a software release, a popular stream or an unusual day; the public notice identifies no such cause here. Repeated traffic says something sturdier about the value of local peering. When two Nepali networks can exchange packets inside Nepal, those packets have a local path available instead of automatically taking a costly international detour. NPIX says this improves service quality and latency. It publishes no before-and-after millisecond figure in the announcement, so the sound claim is about a path becoming available and used.

The members make that path real. In February, NPIX welcomed CAS Cloud, eSewa and East Link. Their arrival shows the mix of networks and services at an exchange, while the April note does not assign them a share of the 100 Gbps. Traffic at an IXP comes from members’ routing choices and customers’ demand, not a switch the exchange chief can simply flip. Shrestha’s old APNIC statement joins technical operations to community governance; the April post shows why the two belong together. A meeting place works only when others keep turning up.

NPIX has daily, weekly and monthly traffic views. Those live graphs are the next place to watch whether local exchange use keeps returning through ordinary weeks, and whether more participants join the fabric. Shrestha’s 100 Gbps headline earned attention. The less glamorous achievement is a local route that members still find worth taking tomorrow.