bgpreport

Network · data from 2026-11-12

AS139982 PT Buana Visualnet Sentra

Registry name: BVSNET-AS-ID - PT Buana Visualnet Sentra, ID · PeeringDB

10IPv4 routes 70.0% RPKI valid · 60.0% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
1No ROA 5 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS139982, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS139982, 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.134.188.0/22 Invalid: origin None 17 3%low visibility 16
103.134.189.0/24 Invalid: origin Other origin only 3 0%low visibility 2
103.97.76.0/23 No ROA Other IRR onlyRADB 2 0%low visibility 2
103.97.77.0/24 Valid Nonecovered by 103.97.76.0/23 673 100% 69
103.66.63.0/24 Valid Other origin onlycovered by 103.66.62.0/23 669 99% 66
2405:cac0:1::/48 Valid Nonecovered by 2405:cac0::/32 635 100% 69
103.66.62.0/23 Valid Other IRR onlyRADB 673 100% 68
103.148.44.0/23 Valid Other IRR onlyRADB 673 100% 69
103.148.44.0/24 Valid Other IRR onlyRADB 673 100% 69
103.148.45.0/24 Valid Other IRR onlyRADB 673 100% 69
103.66.62.0/24 Valid Other IRR onlyRADB 671 100% 68
2405:cac0::/32 Valid Other IRR onlyRADB 605 95% 67

AS-SET

PeeringDB's irr_as_set for AS139982: AS139982:AS-BVSNET. 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 (AS139982 isn't in the set, or no route object for AS139982 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.

NameDatabaseASNsSets Route objectsAS139982 in itNot covered
AS139982:AS-BVSNET APNIC 12154 No 12

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 16 are in fix.csv.

  • ROA: origin2
  • ROA: none1
  • Route object: none5
  • Route object: RIR7
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: origin103.134.188.0/22ROAs covering it name AS58495, not AS139982. If AS139982 should announce it, add a ROA for AS139982.17 of 673
Route object: none103.134.188.0/22No route object for it. Add a route object with origin AS139982 in the RIR database for the space.17 of 673
ROA: origin103.134.189.0/24ROAs covering it name AS58495, not AS139982. If AS139982 should announce it, add a ROA for AS139982.3 of 673
Route object: none103.134.189.0/24Route objects for it name AS58495. Add a route object with origin AS139982 in the RIR database for the space.3 of 673
ROA: none103.97.76.0/23No ROA covers it. Add a ROA for AS139982, maxLength 23.2 of 673
Route object: RIR103.97.76.0/23Route object only in RADB. Add it in the RIR database for the space.2 of 673
Route object: none103.97.77.0/24No route object for it. A route object for 103.97.76.0/23 with origin AS139982 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139982 in the RIR database for the space.673 of 673
Route object: none103.66.63.0/24Route objects for it name AS17819. A route object for 103.66.62.0/23 with origin AS139982 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139982 in the RIR database for the space.669 of 673
Route object: none2405:cac0:1::/48No route object for it. A route object for 2405:cac0::/32 with origin AS139982 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139982 in the RIR database for the space.635 of 636
Route object: RIR103.66.62.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.148.44.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.148.44.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.148.45.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.66.62.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2405:cac0::/32Route object only in RADB. Add it in the RIR database for the space.605 of 636
AS-SET: own ASNAS139982:AS-BVSNETAS139982 isn't in AS139982:AS-BVSNET (APNIC) once expanded. Add AS139982 to it.

Route objects not announced

Every route object with origin AS139982 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.