CAL (Compartmental Access Level) Issue


Last weekend RES put up a BAF over Melbourne Australia. It was around 15-20 layers (sorry forgot to keep count). A few days after the BAF, I drove up north from Melbourne to clear the spine (4+ hours drive each way). Since it was school holidays my wife and on of our children (both lapsed ingress agents) drove up with me.

 I was killing the field inside out grabbing uniques, full deploying and hacking as I went up the spine.

 The southern most spine portal was around 100km drive from the northern spine portal.

 When I attacked the outer most portal (link to portal), I got a CAL error.   It may be worthwhile to note that the second last spine portal was only about 50 meters away and I could attack that no problem.


I tried to report the CAL error via support but my in-game support was stuck on a ticket I reported in August about Adventure Sync, which was fixed in a later update. It turns out the ticket was never cleared. I could not figure out how to start a new ticket.

My wife and son were also there. My wife had not played ingress in more than a month. She may have opened the scanner and hacked a portal earlier in the day but that was about it.

When she attacked the CAL restricted portal it was fine. No CAL message. She destroyed the portal and I could then capture the portal without a CAL issue.


  1.  Why could I attack a portal 50m away from the CAL portal and still get a CAL block?
  2. What does an agent do if they already have an uncleared  ticket (like me) and hit the CAL issue?
  3. Why are old tickets not getting cleared? Is there anything agents can do this clear resolved tickets?
  4. Why do I, who has played almost everyday for the past few months get a CAL block while my wife who has not played for the last few months may except may be an odd hack not get a CAL issue?

Possible Solution

Niantic has a lot of information about me. Recursed twice, 167M lifetime AP, 60 (real) mission days, 42 (real) NL events, 16 anomalies on the ground (excluding BB only anomalies) among others. These stats, should be enough to confirm I am a real agent. The fact that I regularly play all around the world (having completed a MD in each continent) should be obvious if CAL is based on historical agent data.

Even if this was not the case I had been peeling the BAF inside out for a good 15+ layers without a problem. The last portal only ~50 meters away from the second last portal should not be a problem. If I was doing this by myself it would have been a 4+ hour drive (one way) wasted.

This is no more frustrating than driving 4+ hours to put up a field only have it killed by a fake agent. In my experience majority of BAFs were not spoofed down. But from my sample of one, evey/most legitimate attackers are getting hit wit a CAL block.

It seems the CAL approach has just shifted the frustration from builders to attackers. More than that an occasional frustration for builders have turned in to a guaranteed frustration to attackers.

I suggest Niantic establish some sort of hard-to-achieve, secret (if do desired) base line profile (eg. recursed, X in-person events, over a 100M+ AP etc) where the CAL restriction does not apply.  Otherwise you are going to end up with lots of very frustrated agents.

I am happy to provide additional detail if needed.

6 votes

Active · Last Updated

Sign In or Register to comment.