There’s no indication the CNAME hasn’t been updated. It’s a proxied record and resolves in DNS.
dig api.takemytickets.co.in
; <<>> DiG 9.10.6 <<>> api.takemytickets.co.in
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21222
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;api.takemytickets.co.in. IN A
;; ANSWER SECTION:
api.takemytickets.co.in. 300 IN A 104.21.42.94
api.takemytickets.co.in. 300 IN A 172.67.160.120
Cloudflare is returning a 521 error. You can review the troubleshooting steps for that particular error to resolve the origin issue.