i have created a subdomain record using route53 with traffic routing to alb,i cant access with my network ip but is accessible with different network

Traffic is getting routed to an ALB, DNS propagation is happening within few seconds, only things is i cant access the webservice from my laptop through which i created the record, if i ask my friend to check if the he can access the service on subdomain, he is able to access it(he is connected to a different network)

Is there any DNS cache left on your PC terminal, router, etc.?

If i switch to different internet network i was able to access the webservice on subdomain immediatly

From what you say it sounds like there is a problem with the network environment you are using. There are multiple possibilities, such as caches remaining in gateway routers, etc., or the routing system is not working very well to begin with.

its happening with different iam user creating a record from their own internet network, they cant access it but others can soon after creating a record

but the subdomain is accessible from a different network within seconds after being created

Thus the DNS has been cached some where.

If DNS had been Cached then how would my friend access the subdomain and i cant at same moment of time

DNS zones are commonly duplicated in multiple servers to minimize latency and improve reliability. As a result, some users will still get the correct response in case these zones fall out of sync. Yet, others will receive an NXDOMAIN error message for the exact same destination. It all depends on the DNS resolution path.

Often such cases are quite difficult to debug without any visibility into the internal network traffic. Network admins must trace exact pathways between clients, networks, and servers.