Firstly, all portals from getEntities are being returned, as far as I can see. If you look at it in Stock the portals appear perfectly fine. This is an issue partly with IITC, in that the representation of a portal is done as a placeholder if the Timestamp of the portal is 0.
That said, why a portal's timestamp is coming back as 0 is an issue. It's not required for Stock which may be why the Niantic team isn't concerned with it, and IITC may simply have to adapt to it, but it's not necessarily Niantic's issue.
Secondly, there are definitely ghosted fields being displayed here. If they're not visible in the game (i.e. Intel is reporting what the game is telling it) then we're back to questions on the cache.
@ofer2 There's a lot of ghosting of fields this afternoon on the map. I don't know if it's related but the timestamps on all entities in getEntities are also zero.
Should the intel map issues cause any issues with not all portals loading within the scanner application? Friday night, as well as Sunday evening, I had issues viewing portals locally in the scanner app while being at that location. I also had issues when doing a remote view with the key, where I could only view the portal I was trying to remote view, despite there being a handful or even a large amount of portals near to the remote view portal.
Local view are portals that I use frequently for local fielding and being unable to see them in scanner makes for a frustrating attempt to play. Remote view was done at home, while on home WI-FI that was working great (was doing it while I watching/streaming Netflix over WI-FI).
Tonight I destroyed a number of fields, put up my own, but the map still shows both blue and green fields coming out of the portals, Attached is one example.
Fields are still ghosting. Portals taken down almost 2 hours ago. ENL agent even linked them together in the scanner.
11:04AM
**** linked Webster Hills United Methodist Church Christian Life Center (1325 West Lockwood Avenue, St. Louis, MO 63122, USA) to Webster Hills United Methodist Church (1333 West Lockwood Avenue, Webster Groves, MO 63119, USA)
Hi everyone, we know about the issue with ghosting fields on Intel and are currently looking into a fix. I will let you know once there has been more progress made about this bug. Sorry for any inconvenience.
Update: we have identified the cause of the issue and are working on getting a patch out. Seeing as how its relatively late in the day and right before the weekend, we may look to revert the offending code before moving forward instead of trying the fix. If this is the case, we will be re-attempting the fix on monday. In either case, expect Intel to be back to full functionality in a few hours.
Issues should be resolved, please let me know if you see otherwise. We will be monitoring from here. Sorry for the issues and thanks again for bearing with us.
Comments
@ofer2 This is the list of broken tiles I found. 33 in all, and looking at them directly continues to fail for those tiles.
I just loaded this.
The blue field is ghosting. All the blue/green portals without levels are placeholders.
The blue one top right https://intel.ingress.com/intel?ll=52.010569,-0.697706&z=15&pll=52.010569,-0.697706 is P5 (if I select it), the other 2 are unclaimed.
Regarding this list, they all appear to be working again.
@Perringaiden thanks for the report. will investigate.
I had 4 cells this morning that were failing:
But directly after the 11:30am reset/update, there were no failing cells.
I've just had to reload iitc.
2 ghosting blue fields and no portal info (detected by iitc) for any claimed portals.
I hope that isn't deliberate, we need to see the level and health.
Have you got a link to the area?
Ok, so there are two problems here:
Firstly, all portals from
getEntities
are being returned, as far as I can see. If you look at it in Stock the portals appear perfectly fine. This is an issue partly with IITC, in that the representation of a portal is done as a placeholder if the Timestamp of the portal is 0.That said, why a portal's timestamp is coming back as 0 is an issue. It's not required for Stock which may be why the Niantic team isn't concerned with it, and IITC may simply have to adapt to it, but it's not necessarily Niantic's issue.
Secondly, there are definitely ghosted fields being displayed here. If they're not visible in the game (i.e. Intel is reporting what the game is telling it) then we're back to questions on the cache.
https://intel.ingress.com/?ll=52.033152,-0.689145&z=17
I'm getting very odd data for some of the portals.
I think that portal should be green - I've not been out to reclaim it. Actually someone else just killed it.
Has this info layout changed recently?
IITC isn't displaying the portal level or health.
That screen is after a getPortalDetails call, which contains the Timestamp.
Except for no timestamp on the getEntities calls, this is totally an IITC issue so should be discussed in the relevant IITC channels.
@ofer2 There's a lot of ghosting of fields this afternoon on the map. I don't know if it's related but the timestamps on all entities in
getEntities
are also zero.Disregard. Looks like there was a reset/update that has fixed it, and the ghost fields that I knew of appear to be gone and the timestamps are back.
They could break IITC daily if they wanted to.
True, though this is a specific case, and the IITC team is looking at ways to cope with it.
Cant see lots of portals now on Intel. Please fix it soon. See links and fields.
Should the intel map issues cause any issues with not all portals loading within the scanner application? Friday night, as well as Sunday evening, I had issues viewing portals locally in the scanner app while being at that location. I also had issues when doing a remote view with the key, where I could only view the portal I was trying to remote view, despite there being a handful or even a large amount of portals near to the remote view portal.
Local view are portals that I use frequently for local fielding and being unable to see them in scanner makes for a frustrating attempt to play. Remote view was done at home, while on home WI-FI that was working great (was doing it while I watching/streaming Netflix over WI-FI).
Could you find any information with the coordinates I provided to you?
Unfortunately no.
Tonight I destroyed a number of fields, put up my own, but the map still shows both blue and green fields coming out of the portals, Attached is one example.
We can see the same issue all over the world. It started a few hours ago
Codename: @ikimonofun
https://intel.ingress.com/intel?ll=35.349394,139.631093&z=16&pll=35.349522,139.631981
Type of Issue:: Crossing link (Enl. RES. links both)
Approximate time of incident: 2020/02/07
P.S.
I know "Maintenance on Intel Map" had finished, but Intel map still has bug.
Thnaks!
Yet another ghost links/fields report.
Fields are still ghosting. Portals taken down almost 2 hours ago. ENL agent even linked them together in the scanner.
11:04AM
**** linked Webster Hills United Methodist Church Christian Life Center (1325 West Lockwood Avenue, St. Louis, MO 63122, USA) to Webster Hills United Methodist Church (1333 West Lockwood Avenue, Webster Groves, MO 63119, USA)
Hi everyone, we know about the issue with ghosting fields on Intel and are currently looking into a fix. I will let you know once there has been more progress made about this bug. Sorry for any inconvenience.
Update: we have identified the cause of the issue and are working on getting a patch out. Seeing as how its relatively late in the day and right before the weekend, we may look to revert the offending code before moving forward instead of trying the fix. If this is the case, we will be re-attempting the fix on monday. In either case, expect Intel to be back to full functionality in a few hours.
Thanks.
Issues should be resolved, please let me know if you see otherwise. We will be monitoring from here. Sorry for the issues and thanks again for bearing with us.
We had an issue today, a few hours ago where links and fields were ghosting in game, as well as on intel.
Seemed to be working again a few minutes later, and thought that it was rolled back, again.
Since the weekend, can @NianticCasey or @NianticBC confirm that it is indeed fixed?
and whether the team is now onto the physical server backend (ie not the intel server)?