静态扫描处理延迟
Pending
受影响的组件
Static Analysis Services
- investigating
我们目前正在调查这一问题.
- investigating
我们正在继续调查这一问题.
- identified
这一问题已经确定,一个解决办法正在实施之中.
- monitoring
一项措施已经执行,我们正在监测结果.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
61 Veracode incidents · 2025年3月 — official updates, affected components, duration and resolution details.
我们目前正在调查这一问题.
我们正在继续调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在研究这个问题
我们正在继续调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
监测 - 问题似乎已经解决
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查造成政策计算比预期时间长的拖延.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
Veracode检测到了一些客户比正常的静态扫描完成时间长. 一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some users are seeing the maintenance page. Investigation is underway.
This incident is being monitored. The impact of this issue appears to be limited to requests that originate within the Veracode network.
This incident has been resolved.
在浏览用户界面时,用户可能会被重定向到您的账户设置.
这一问题已经确定,一个解决办法正在实施之中.
我们正在继续努力解决这个问题。
一项措施已经执行,我们正在监测结果.
事件期间提交的一些静态扫描可能仍然处于卡住状态. Veracode正在工作 通过让他们处理.
我们正在继续处理积压的被粘住的静态扫描.
我们处理完毕积压的静态扫描 在某些情况下,我们无法处理失败的扫描。 在这种情况下,扫描应被删除并重新上载.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决。 客户使用Veracode平台或API在后期之间可能已经看到Veracode API的登录问题或500个关卡响应. - 6:20 AM EDT - 7:00 AM EDT - 8:20 AM EDT - 9:05 AM EDT
自动翻译自官方事件更新。
我们目前正在调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
SCA继续接受维修,并将尽快提供.
我们正在继续努力完成维修工作。 在此期间,其他Veracode API会看到出错率上升.
维修工作已经完成,测试工作正在完成。 API 出错率已解决 .
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在追踪与获取或编辑政策信息有关的更多错误。 扫描服务和政策评价没有受到影响.
修好了,交通正常进行.
这一事件已经得到解决.
自动翻译自官方事件更新。
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are investigating the issue
We have identified the issue and working on the fix
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.