Network · data from 2026-11-12

AS150480 Bursa Networking

Registry name: BURSANET-AS-ID - PT Swara Logika Laboratory, ID · PeeringDB

3IPv4 routes 100.0% RPKI valid · 33.3% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 2 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS150480, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS150480, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


103.49.50.0/24	Valid	Nonecovered by 103.49.50.0/23	673 100%	69
103.49.51.0/24	Valid	Nonecovered by 103.49.50.0/23	673 100%	69
103.49.50.0/23	Valid	Other IRR onlyRADB	673 100%	69
2001:df3:1040::/48	Valid	Other IRR onlyRADB	635 100%	70

AS-SET

PeeringDB's irr_as_set for AS150480: AS150480:AS-BURSANET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS150480 isn't in the set, or no route object for AS150480 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS150480 in it	Not covered
AS150480:AS-BURSANET	RADB	1	1	2	Yes	0

Name

Database

ASNs

Sets

Route objects

AS150480 in it

Not covered

AS150480:AS-BURSANET

RADB

Yes

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.

Route object: none2
Route object: RIR2

Change	Prefix or set	Detail	Full-table peers
Route object: none	103.49.50.0/24	No route object for it. A route object for 103.49.50.0/23 with origin AS150480 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150480 in the RIR database for the space.	673 of 673
Route object: none	103.49.51.0/24	No route object for it. A route object for 103.49.50.0/23 with origin AS150480 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150480 in the RIR database for the space.	673 of 673
Route object: RIR	103.49.50.0/23	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	2001:df3:1040::/48	Route object only in RADB. Add it in the RIR database for the space.	635 of 636

Change

Prefix or set

Detail

Full-table peers

Route object: none

103.49.50.0/24

No route object for it. A route object for 103.49.50.0/23 with origin AS150480 covers it (filters allowing more-specifics accept it). Add a route object with origin AS150480 in the RIR database for the space.

673 of 673

Route object: none

103.49.51.0/24

673 of 673

Route object: RIR

103.49.50.0/23

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

2001:df3:1040::/48

Route object only in RADB. Add it in the RIR database for the space.

635 of 636

Route objects not announced

Every route object with origin AS150480 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.