Is API down? 3 Aug 2022

c_harish

@admin any issues with API? not able to generate tokens or login. please check.

c_harish

@admin
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Read timed out. (read timeout=7)

admin

Hi @c_harish , request you to please share more information

is your code on local or AWS ? can you please help me with
are you using Angel official library ? if yes, which language?
API end point which is not working
Error message from Angel API
Timing of the issue

c_harish

@admin it is fine now.. started working @ 9:25 am. Am I the only one who faced this? did you guys get any other report of such issues @ today market open?

code hosted in aws amazon linux.
yes. using official smartapi python library.
token generation wasn't working. so couldn't proceed to further endpoints.. no idea if other endpoints were also down.
"requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='apiconnect.angelbroking.com', port=443): Read timed out. (read timeout=7)"
from 9:05 to 9:25.. from 9:26 am, it started working fine.

@StocksDeveloper was it fine for you guys?

also lately from last 1 week,

"NIFTY HARISH Couldn't parse the JSON response received from the server: b'<!doctype html><html lang="en"><head><title>HTTP Status 500 \xe2\x80\x93 Internal Server Error</title><style type="text/css">body {font-family:Tahoma,Arial,sans-serif;} h1, h2, h3, b {color:white;background-color:"

this error is creeping up often. we didn't face this issue much for past 3 months. now it is coming back again.

ravitandur

@c_harish Hi Harish, thank you for reporting this issue. I also faced similar issue and reported the same to Angel team.
https://smartapi.angelbroking.com/topic/2229/getting-lot-of-read-timed-out-from-angel
I started facing this issue from Monday.
I shared all details requested and waiting from Angel to get the root cause for the issue.
As u mentioned the issue was there from 9:15 to 9:31 for me.

c_harish

@ravitandur thanks for reporting, Ravi. This isn't something new. Used to happen a lot in past. For the past 3-4 months, didn't face much of this issue. But now it is starting to come back. Lets hope @admin finds the issue and fixes it once and for all.