Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


polki

24 posts

Geek


#96390 26-Jan-2012 13:10
Send private message

Getting online lag that resembles packet loss issues I've had before.  Last night had some packet loss on pingtest.net then rebooted modem and was gone.  Ran 3 ping tests to different servers including Australia with no loss.  Playing games today noticed some similar lag to yesterday.  Ping test results below.  Does it look like my router is at fault for this?   Router is running gargoyle 1.4.5 firmware.  Test computer is currently setup as DMZ in gargoyle.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

ping 113.21.225.162 -n 100

Pinging 113.21.225.162 with 32 bytes of data:
Reply from 113.21.225.162: bytes=32 time=204ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination port unreachable.
Reply from 113.21.225.162: bytes=32 time=161ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=457ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=291ms TTL=119
Reply from 113.21.225.162: bytes=32 time=26ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination port unreachable.
Reply from 113.21.225.162: bytes=32 time=775ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=197ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 192.168.1.1: Destination net unreachable.

Ping statistics for 113.21.225.162:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 775ms, Average = 41ms


Rebooted router again and re-ran ping test.

ping 113.21.225.162 -n 100

Pinging 113.21.225.162 with 32 bytes of data:
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination port unreachable.
Reply from 113.21.225.162: bytes=32 time=412ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=138ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=271ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Request timed out.
Reply from 192.168.1.1: Destination port unreachable.
Reply from 113.21.225.162: bytes=32 time=712ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=2078ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 192.168.1.1: Destination net unreachable.
Reply from 192.168.1.1: Destination port unreachable.
Reply from 113.21.225.162: bytes=32 time=523ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=1886ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=19ms TTL=119
Reply from 113.21.225.162: bytes=32 time=23ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119
Reply from 113.21.225.162: bytes=32 time=18ms TTL=119
Reply from 113.21.225.162: bytes=32 time=22ms TTL=119
Reply from 113.21.225.162: bytes=32 time=21ms TTL=119
Reply from 113.21.225.162: bytes=32 time=20ms TTL=119

Ping statistics for 113.21.225.162:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 2078ms, Average = 82ms

 
Thanks for your help.
Van.

Create new topic
Ragnor
8035 posts

Uber Geek

Trusted

  #573583 26-Jan-2012 13:38
Send private message

Are you connected to the device by network cable or wireless?

If by wireless:
- Do you get the same problem via network cable?
- Try Wi Lan Optimizer, it stops Windows background scanning for available wifi networks from causing this
http://www.martin-majowski.de/wlanoptimizer/


If by network cable:
- Have you tried plugging directly into your modem (I presume you have a separate modem) to check whether you're getting the same problem? This would probably let you confirm whether it's a ISP issue rather than a device issue.

polki

24 posts

Geek


  #573585 26-Jan-2012 13:40
Send private message

Thanks for the reply.
I am connect by 2m cat5e cable to router, router to modem over 20m cat5e.  Modem is setup for ip passthrough to the router.
I will try the test connect directly to the router with ip passthrough and post results.
Thanks
Van 

 
 
 
 


polki

24 posts

Geek


  #573588 26-Jan-2012 13:46
Send private message

Connected directly to modem over 20m cat5e.
Results:

ping 113.21.225.162 -n 100

Pinging 113.21.225.162 with 32 bytes of data:
Reply from 113.21.225.162: bytes=32 time=761ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=23ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=17ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=867ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=25ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=641ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=1909ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=22ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=21ms TTL=120
Reply from 113.21.225.162: bytes=32 time=18ms TTL=120
Reply from 113.21.225.162: bytes=32 time=20ms TTL=120
Reply from 113.21.225.162: bytes=32 time=19ms TTL=120

Ping statistics for 113.21.225.162:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 1909ms, Average = 60ms

Still got big ping spikes but none of the 192.168.1.1 issues.
BTW ISP is slingshot so I dont expect awesome performance.

Create new topic





News »

Nanoleaf enhances lighting line with launch of Triangles and Mini Triangles
Posted 17-Oct-2020 20:18


Synology unveils DS1621+ 
Posted 17-Oct-2020 20:12


Ingram Micro introduces FootfallCam to New Zealand channel
Posted 17-Oct-2020 20:06


Dropbox adopts Virtual First working policy
Posted 17-Oct-2020 19:47


OPPO announces Reno4 Series 5G line-up in NZ
Posted 16-Oct-2020 08:52


Microsoft Highway to a Hundred expands to Asia Pacific
Posted 14-Oct-2020 09:34


Spark turns on 5G in Auckland
Posted 14-Oct-2020 09:29


AMD Launches AMD Ryzen 5000 Series Desktop Processors
Posted 9-Oct-2020 10:13


Teletrac Navman launches integrated multi-camera solution for transport and logistics industry
Posted 8-Oct-2020 10:57


Farmside hits 10,000 RBI customers
Posted 7-Oct-2020 15:32


NordVPN starts deploying colocated servers
Posted 7-Oct-2020 09:00


Google introduces Nest Wifi routers in New Zealand
Posted 7-Oct-2020 05:00


Orcon to bundle Google Nest Wifi router with new accounts
Posted 7-Oct-2020 05:00


Epay and Centrapay partner to create digital gift cards
Posted 2-Oct-2020 17:34


Inseego launches 5G MiFi M2000 mobile hotspot
Posted 2-Oct-2020 14:53









Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Support Geekzone »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.