MS Team Performance issue with SIFY

Question

We need a tracert return to SIFY IP-118.94.145.164. I wanted to reach out regarding the ongoing challenges we are experiencing with MS Teams meetings at both our Kolkata and Jamshedpur offices, which are having on the SIFY ISP link

Answer 1

Hi Ghosh, Partha,

To help investigate the Microsoft Teams performance issue over the SIFY ISP link, please run the following network checks from both the Kolkata and Jamshedpur offices while connected to the SIFY network.

1/ Run traceroute to Microsoft 365 endpoints:

• tracert outlook.office365.com
• tracert world.tr.teams.microsoft.com

2/ Run traceroute to the SIFY IP mentioned in your report:

• tracert 118.94.145.164

3/ Run a basic latency check:

• ping outlook.office365.com

You can share the full results from both locations. Comparing the routing path and latency between the two offices can help determine whether the issue occurs within the SIFY network path or elsewhere on the route to Microsoft 365 services.

Looking forward to your update.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment."    

If you want to receive the related email notification for this thread, please follow the steps in our documentation to enable e-mail notifications.

Answer 2

Run the following checks from both Kolkata and Jamshedpur sites while connected via the SIFY ISP link to isolate where the Teams performance issue occurs.

1. Run traceroute to Microsoft 365 front doors From a Windows client at each site, run:
   • tracert outlook.office365.com
   • tracert world.tr.teams.microsoft.com
   • If using SharePoint/OneDrive heavily, also: tracert microsoft.sharepoint.com
   Compare the hops, latency, and any timeouts between:
   • Kolkata → Microsoft 365
   • Jamshedpur → Microsoft 365
   Look for:
   • Sudden latency jumps at or just after SIFY-owned hops.
   • Packet loss or repeated * * * timeouts in the SIFY segment.
2. Run traceroute to the SIFY IP From the same clients, run:
   • tracert 118.94.145.164
   Use this to:
   • Confirm the path from each office to the SIFY IP.
   • Identify whether routing asymmetry or extra WAN hops exist for one site.
3. Measure latency and bandwidth a. Latency to Microsoft 365
   • Use ping outlook.office365.com to see the front-door region and basic RTT.
   • For more accurate RTT over TCP 443, use PsPing as described:
     • psping -4 outlook.office365.com:443
     • psping -4 -n 20 yourTenant-my.sharepoint.com:443
   • Compare average RTT from both sites. Consistently high RTT on the SIFY path will directly impact Teams.
   b. Bandwidth
   • From each site, run an online speed test (for example, a site found by searching for speed test) while connected via SIFY.
   • Compare measured upload/download against what SIFY is contracted to provide.
   • If bandwidth is consistently below expectation, escalate to SIFY with screenshots and timestamps.
4. Check Microsoft 365 connectivity end-to-end
   • Run the Microsoft 365 network connectivity test tool from each office.
   • Review:
     • HTTP/HTTPS connectivity to required Microsoft 365 endpoints.
     • TLS/SSL inspection or interception by any middleboxes.
     • Traceroute results to Exchange Online, SharePoint, and Teams front doors.
   • Any failed or intercepted endpoints, or unusual detours in the path, should be shared with SIFY and the internal network team.
5. Analyze traces if deeper troubleshooting is needed If Teams slowness is specific to Microsoft 365 traffic:
   • Capture a short Netmon or Wireshark trace while reproducing the issue.
   • Identify Microsoft 365 traffic as described (filter by URL or IP, use Conversation IDs).
   • Check for:
     • High DNS resolution times (dns.time column in Wireshark).
     • Suboptimal TCP Max Segment Size (MSS) in SYN/SYN-ACK (goal is 1460 bytes).
   • If DNS or MSS issues appear only when traversing the SIFY path, include these findings in the ISP escalation.
6. Engage SIFY with concrete data Provide SIFY with:
   • Traceroute outputs to outlook.office365.com, world.tr.teams.microsoft.com, and 118.94.145.164 from both sites.
   • Ping/PsPing RTT statistics.
   • Speed test results vs contracted bandwidth.
   • Any Microsoft 365 network connectivity test insights indicating blocked or intercepted endpoints.
   Ask SIFY to:
   • Verify routing and peering from both locations to Microsoft 365 front doors.
   • Check for congestion, QoS misconfiguration, or packet loss on their network.
7. Internal network checks In parallel, ensure:
   • Local firewalls/proxies are not blocking or intercepting Microsoft 365 optimize/allow endpoints listed at https://aka.ms/o365ip.
   • VPN split tunneling is configured for Microsoft 365/Teams traffic if VPN is in use, following the guidance in “Implementing VPN split tunneling for Office 365”.
   • QoS for Teams media is implemented as per “Implement Quality of Service in Microsoft Teams”.

These steps will give a clear view of whether the performance issue is caused by the SIFY path, local network devices, or general Internet routing, and provide the necessary evidence for ISP and internal network teams to remediate.

---

References:

• Microsoft 365 network connectivity test tool
• Performance troubleshooting plan for Microsoft 365
• How to improve your internet connection for better call quality in Microsoft Teams