# Portal Neutral Time

✭✭✭✭
edited April 2021 in General

What determines the portal neutral time?

Because I am used to playing regularly when I go to work, I found the answer, which is the time when deploy the first resonator (capture). For example, I captured portal A on Monday at 07.00 am, then the portal will self-neutral for the next 1 week at the same time (if the portal is not attacked). Is that true?

I've been paying attention to this at least during the pandemic and jotting down phone reminders as an alarm.

But I've found some portals don't neutral at the same hour, so I waited for about 10 minutes for the portals to decay, even though other portals on the route have neutral the same as last week.

Because I didn't want to be late for the office, I continued my journey by capturing and fielding the portal in front of her as usual. And don't forget to record the change in time on the phone reminder.

And yesterday my friend also found the same thing, some portals do not neutral at the same time as last week.

How did it happen?

What do you think? What determines the timing of the portal neutral?

Post edited by Lightseagreen on
Tagged:

• edited April 2021

If you mean portal decay, it occurs exactly 24 hours after the portal was captured.

So if Portal A was captured at 9:05 and portal B was captured at 9:07, then Portal A will decay at 9:05 the next day and Portal B will decay at 9:07 the next day.

On the 7th day, the remaining 10% left on the portal will die at 9:05 for portal A and 9:07 for portal B.

If you recharge, it will last longer, but it'll still decay at the same time each day.

• ✭✭✭✭
edited April 2021

yes, thank you, it means that my assumption is correct.

But as I asked in the post, I've found several portals not decay (neutral) at the same hour on the 7th day.

Continuing the example you mentioned, portal C was captured at 09.09, portal D was captured at 09.11 and portal E was captured at 09.13.

Portals A, B and E will neutral same time on the 7th day but portals C and D are not. Portals C and D are not neutral at the same time. The 2 portals were neutral after I arrived at the office about 30 minutes from portal E

• ✭✭✭✭✭

@RushdieRR It may be that the decay times aren't precise, and that it happens "at or a little after" the scheduled decay time. If this happened in the last couple of day we know from another discussion that Niantic is having some server issues, with the intel map being a bit slow and some people having trouble logging in. In fact, I'm staring at a black "No Ingress for you!" screen right this minute.

My experience has been that decay times are usually pretty accurate but not always.

• ✭✭✭✭

Yes, same as me a few hours ago having trouble logging in.

For decay times aren't precise, I experienced it once about 2 months ago (can't remember whether there was an increase in latency at that time) and my friend had it yesterday.

• ✭✭✭✭

@Hosette @Perringaiden Can we change the portal decay time?

I once filled the resonators into portal near my house which left 2 resonators after an attack, then I deploy the 3rd to 8th resonators, then I recharged them completely.

The next day I found that the portal's decay time had changed to the time when I deploy the reso to 3-8, was not the first capture time.

But it doesn't work on portals that have 3 resonators / more.

have you ever experienced something like that?

• ✭✭✭

i can confirm too, the decay times are very rarely not correct 🙈 I keep very good track of it because it are mostly decay times of certain portals.

• ✭✭✭✭

how many times have you found it? Is it in the last few days?

• ✭✭✭✭

When it's first captured sets time. There might be a little variance, but if you know exactly when you put the first reso in, you know that 167 hours and 50 minutes later you better revisit or recharge or the portals, links and mods go poof.

• Can we change the portal decay time?

Sure. Let the portal die and recapture it at a new time. Otherwise, no.

• ✭✭✭

no. not in last couple of days. 2 or 3 x times a year ? 🤷‍♀️

• ✭✭✭

Using a battle beacon resets it. I guess it's due to it flipping and then being recaptured by ADA/Jarvis so it's treated as a new capture.

• ✭✭✭✭✭

That's interesting because I'm fairly sure that using an ADA or Jarvis doesn't reset the time.

• ✭✭✭✭✭

If the portal is not decayed at the time you expect (and hasn't been recharged in the meantime) it could be due to scanner lag or server lag. I suggest trying to recharge one resonator on the portal and see if it updates. If it's scanner lag, the server will tell you that you can't recharge it because the portal is neutral. If it's server lag, maybe the server will recalculate and neutralise the portal when you prod it - or maybe it won't. Who knows - but it might be an interesting experiment.

• ✭✭✭✭

the server will tell you that you can't recharge it because the portal is neutral.

I've come across something similar to this. When I was at portal A, I saw portal B in front of neurtal (see neurtal animation), after I finished with portal A then switched to portal B, when I captured portal B warning there was no slot to fill, then I logged out and returned to log in, I saw the portal was still healthy (10%) with 8 resonators, but when I try to link, a neurtal portal warning appears. This happened about 1 month ago.

but it might be an interesting experiment.

yes for me this is interesting because of that I try to share my experience.

• Someone should science this and come back to us with results :-)

• cannot reproduce. can you?

• ✭✭✭✭

i only discovered it once by accident and as far back as I can remember. Unfortunately I didn't record it while I was playing. Same thing when I found the decay times aren't precise

• So can we get the information about when will the portal be neutralized in intel map?

• ✭✭✭✭

Portal decay was randomized for a while with portals getting no decay, normal decay, or double decay. It seems to have reverted to the previous non random mode at present.

• This used to exist on the Intel Map (and definitely exists on the server) but it was removed way back in 2014 when someone killed Joe Philley's Guardian and he wigged out (despite years of making fun of people complaining about lost guardians).

There used to be a Capture Date/Time which meant you could calculate exactly when an unrecharged portal would decay-neutralize.

Given Guardian is no longer a thing, there's a real case for @NianticBrian to rule that the Capture Date/Time should be returned to the Intel map's user accessible data.

• ✭✭✭✭✭

Huh

Capture date was added to intel around spring/summer 2013. It was removed before the end of the year due to the guardian influence. I'm pretty sure the stat existed before the agent profiles were introduced in September 2013. That's the only reason I was lucky to get onyx guardian after New Year's 2014.

• I got my Guardian in Feb 2014, and it existed after that point. It only became a problem after Level 9 was added in early 2014.

• ✭✭✭✭✭

The date was on the map. The time was not (which means it doesn't help with this request). The date was removed on 16 June 2014.

Intel map data currently has a 'last touched' timestamp for each portal, but it's not shown in the user interface (rumour is that there might be an IITC plugin for it). If the portal is alive but hasn't been visited or recharged recently then this timestamp indicates the most recent resonator decay.

• Date was formatted on stock. The time was always there in the data and visible in IITC because a timestamp is a timestamp not a datestamp.

Intel map data currently has a 'last touched' timestamp for each portal, but it's not shown in the user interface

Yep. And there's a dozen ways to read it with or without IITC (but without takes more IT knowledge).

If the portal is alive but hasn't been visited or recharged recently then this timestamp indicates the most recent resonator decay.

The problem is knowing that, since all manner of things update it. That only really works for remote portals no-one interacts with.