Codecov throws 403 when generating Report

Hi Folks,

we have been using Codecov for our unit test coverage. I see that since today morning, it is throwing 403 when generating reports. Is this something known? Can anyone help me?

{ statusCode: 403,
body: ‘<?xml version="1.0" encoding="UTF-8"?>\nSignatureDoesNotMatchThe request signature we calculated does not match the signature you provided. Check your key and signing method./codecov/v4/raw/2019-04-10/32A3AC49B13B24336557E0E233A60ED4/2a781fe99cc03672c8f10aad2c65ccd7f764a659/5cba350b-4402-4ef6-86f5-a8e3a5a0d904.txt15943A35EA40A07F3L137’,
headers:
{ server: ‘nginx/1.13.12’,
date: ‘Wed, 10 Apr 2019 21:29:34 GMT’,
‘content-type’: ‘application/xml’,
‘transfer-encoding’: ‘chunked’,
connection: ‘close’,
vary: ‘Accept-Encoding, Origin’,
‘accept-ranges’: ‘bytes’,
‘content-security-policy’: ‘block-all-mixed-content’,
‘x-amz-request-id’: ‘15943A35EA40A07F’,
‘x-xss-protection’: ‘1; mode=block’,
‘strict-transport-security’: ‘max-age=15724800; includeSubDomains’ },
request:
{ uri:
Url {
protocol: ‘https:’,
slashes: true,
auth: null,
host: ‘codecov.io’,
port: 443,
hostname: ‘codecov.io’,
hash: null,
search: ‘?AWSAccessKeyId=AKIAIHLZSCQCS4WIHD4A&Expires=1554931784&Signature=jFboUnOE2E7qNGq5KzXZts0Ijys%3D’,
query: ‘AWSAccessKeyId=AKIAIHLZSCQCS4WIHD4A&Expires=1554931784&Signature=jFboUnOE2E7qNGq5KzXZts0Ijys%3D’,
pathname: ‘/codecov/v4/raw/2019-04-10/32A3AC49B13B24336557E0E233A60ED4/2a781fe99cc03672c8f10aad2c65ccd7f764a659/5cba350b-4402-4ef6-86f5-a8e3a5a0d904.txt’,
path: ‘/codecov/v4/raw/2019-04-10/32A3AC49B13B24336557E0E233A60ED4/2a781fe99cc03672c8f10aad2c65ccd7f764a659/5cba350b-4402-4ef6-86f5-a8e3a5a0d904.txt?AWSAccessKeyId=AKIAIHLZSCQCS4WIHD4A&Expires=1554931784&Signature=jFboUnOE2E7qNGq5KzXZts0Ijys%3D’,
},
method: ‘PUT’,
headers:
{ ‘Content-Type’: ‘plain/text’,
‘x-amz-acl’: ‘public-read’,
‘content-length’: 505322 } } }
Exited with code 1

Hey, @gopal we experienced a bit of 403 a couple days ago. Are you still seeing this error?