NETWORK

TEDDYBEAR · September 28, 2012, 12:29:25 PM

Can anyone please confirm if the network is up and running OK.
I have a red box with Network Not Connected. The Process Hardware Flights box is ticked.

Thanks
Bryan

FACTflights · September 29, 2012, 09:27:34 AM

Hi Teddy Bear,

Click on the "NETWORK" box next to "MY FLIGHTS" then go to the left bottom and click"GET FLIGHTS FROM RADARBOX NETWORK"

TEDDYBEAR · September 29, 2012, 09:47:20 AM

Thanks FACTflights.
Now up and running. Was on My Flights with the box ticked not Network.

Bryan

darkskies74 · October 14, 2012, 03:33:08 AM

Hi all, does anyone know if there is a network problem at present? I am seeing way too many network a/c for my area, and it is apparent they are not moving. Have restarted several times today to no avail.
Pic file enclosed.
Phil

Kenny · October 14, 2012, 04:49:34 AM

This morning I saw the network number spiked to 6000 for 1-2 minutes. I'm sure that it was unreal.

Undertaker · October 14, 2012, 07:40:46 AM

My Box is showing 8190 from the Network at 0840Z, also the screen is cluttered with old radar returns from the Network [ie Heathrow]

vonsmalhausen · October 14, 2012, 07:53:19 AM

same here, up to well over 8000 hits ; completely freezing the program up
have this since yesterday evening, only way to use the RB is to untick the network

carras320 · October 14, 2012, 09:35:35 AM

Mine the same problem. Freezed at moments too much contacts at the same time?.

Cheers!

Chris11 · October 14, 2012, 10:37:33 AM

Well at least we know that ANRB can't handle 8000 aircraft ;)

My screen is frozen as well

jdsd · October 14, 2012, 10:41:12 AM

I have had to switch the network off,only way I can get mine to work without freezing

JD

Runway 31 · October 14, 2012, 10:52:30 AM

I would think that the problems are associated with the ongoing maintenance work http://www.airnavsystems.com/forum/index.php?topic=7239.0

Airnav Support have been advised of problems just in case they were not aware.

Alan

AirNav Development · October 14, 2012, 01:06:13 PM

We've been working on some database optimization and the last release was deployed to the server 9 hours ago.
It happened that the routine that cleaned the database from timeout flights was failing thus old flights were still kept there. The problem is solved at this time.

Please accept our apologies for this problem - everything should be working OK now.