Please let me know if there is a way of reaching our instances quickly. The below mentioned is the details about my personal development instance.
This is our development instance which is available here https://sifytest.service-now.com/nav_to.do?
The pathping details to our development site is as mentioned here.
Hi,
Is your concern that there are too many hops before a packet reaches the destination?
Since it's accessed via the cloud, data travels through the internet so standard networking rules apply.
If you want less hops you would need to look to invest in leased lines, etc. and contact your ISP.
Dear Mr. Darius Koohmarey(sir),
Yes, this is one of my concern and also requesting you to let me know your findings in improving our ways of reach ability to our instances.
Thank you,
Sir,
I don't know what was done. Please find the IP details as I have been checking from past few days for both our production and development instances and it has reduced.
ServiceNow development instance: pathping sifydev.service-now.com
Tracing route to sifydev.service-now.com [103.23.66.100]
over a maximum of 30 hops:
0 13161-MAA [192.168.98.226]
1 lan-202-144-64-76.maa.sify.net [202.144.64.76]
2 221-135-169-182.sify.net [221.135.169.182]
3 100.65.150.194
4 203.208.192.213
5 203.208.171.170
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 13161-MAA [192.168.98.226]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% lan-202-144-64-76.maa.sify.net [202.144.64.76]
0/ 100 = 0% |
2 3ms 0/ 100 = 0% 0/ 100 = 0% 221-135-169-182.sify.net [221.135.169.182]
0/ 100 = 0% |
3 36ms 0/ 100 = 0% 0/ 100 = 0% 100.65.150.194
0/ 100 = 0% |
4 35ms 0/ 100 = 0% 0/ 100 = 0% 203.208.192.213
100/ 100 =100% |
5 --- 100/ 100 =100% 0/ 100 = 0% 203.208.171.170
Trace complete.
ServiceNow test instance: pathping sifytest.service-now.com
Tracing route to sifytest.service-now.com [103.23.67.100]
over a maximum of 30 hops:
0 13161-MAA [192.168.98.226]
1 lan-202-144-64-76.maa.sify.net [202.144.64.76]
2 221-135-169-182.sify.net [221.135.169.182]
3 100.65.150.194
4 203.208.192.213
5 203.208.158.209
6 203.208.171.33
7 203.208.152.74
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 13161-MAA [192.168.98.226]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% lan-202-144-64-76.maa.sify.net [202.144.64.76]
0/ 100 = 0% |
2 2ms 0/ 100 = 0% 0/ 100 = 0% 221-135-169-182.sify.net [221.135.169.182]
0/ 100 = 0% |
3 35ms 0/ 100 = 0% 0/ 100 = 0% 100.65.150.194
0/ 100 = 0% |
4 35ms 0/ 100 = 0% 0/ 100 = 0% 203.208.192.213
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% 203.208.158.209
0/ 100 = 0% |
6 68ms 0/ 100 = 0% 0/ 100 = 0% 203.208.171.33
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% 203.208.152.74
Trace complete.
Sify internal ticketing system
C:\Users\13161>pathping mitsioni.sify.net
Tracing route to mitsioni.sify.net [119.226.135.165]
over a maximum of 30 hops:
0 13161-MAA [192.168.98.226]
1 lan-202-144-64-76.maa.sify.net [202.144.64.76]
2 221-135-169-182.sify.net [221.135.169.182]
3 100.66.10.9
4 119.226.135.188
5 119.226.135.165
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 13161-MAA [192.168.98.226]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% lan-202-144-64-76.maa.sify.net [202.144.64.76]
0/ 100 = 0% |
2 2ms 0/ 100 = 0% 0/ 100 = 0% 221-135-169-182.sify.net [221.135.169.182]
0/ 100 = 0% |
3 25ms 0/ 100 = 0% 0/ 100 = 0% 100.66.10.9
0/ 100 = 0% |
4 25ms 0/ 100 = 0% 0/ 100 = 0% 119.226.135.188
0/ 100 = 0% |
5 25ms 0/ 100 = 0% 0/ 100 = 0% 119.226.135.165
Trace complete.
Sify customer ticketing system login.
This is what I am getting for our ticketing tool which is ioni.
Thank you for your concern and help.
This document was generated from the following discussion: Increasing ip reachability to our instance.
