bgpreport

Network · data from 2026-11-12

AS55832 HOME SYSTEMS PVT LTD.

Registry name: HOMESYSTEM-AS-AP - HOME SYSTEMS PVT.LTD, IN · PeeringDB

23IPv4 routes 30.4% RPKI valid · 30.4% with a route object
5IPv6 routes 100.0% RPKI valid · 100.0% with a route object
8RPKI invalid 8 origin · 0 maxLength
8No ROA 16 with no route object for this origin
19Low visibility seen by under 10% of full-table peers
27Route objects not announced registered with origin AS55832, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55832, 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.

45.64.208.0/24 Invalid: origin Other origin only 4 1%low visibility 3
45.64.209.0/24 Invalid: origin Other origin only 4 1%low visibility 3
45.64.210.0/24 Invalid: origin Other origin only 4 1%low visibility 3
45.64.211.0/24 Invalid: origin Other origin only 4 1%low visibility 3
103.245.104.0/24 Invalid: origin Other origin only 4 1%low visibility 3
103.245.105.0/24 Invalid: origin Other origin only 4 1%low visibility 3
103.245.106.0/24 Invalid: origin Other origin only 4 1%low visibility 3
103.245.107.0/24 Invalid: origin Other origin only 4 1%low visibility 3
120.88.180.0/24 No ROA Nonecovered by 120.88.176.0/20 4 1%low visibility 4
120.88.181.0/24 No ROA Nonecovered by 120.88.176.0/20 4 1%low visibility 4
120.88.182.0/24 No ROA Nonecovered by 120.88.176.0/20 4 1%low visibility 4
120.88.183.0/24 No ROA Nonecovered by 120.88.176.0/20 4 1%low visibility 4
120.88.184.0/24 No ROA Nonecovered by 120.88.176.0/20 4 1%low visibility 4
120.88.185.0/24 No ROA Nonecovered by 120.88.176.0/20 4 1%low visibility 4
120.88.186.0/24 No ROA Nonecovered by 120.88.176.0/20 4 1%low visibility 4
120.88.187.0/24 No ROA Nonecovered by 120.88.176.0/20 4 1%low visibility 4
27.123.216.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
27.123.217.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
27.123.218.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
27.123.219.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
2407:2a00::/32 Valid RIR databaseAPNIC 635 100% 67
2407:2a00::/44 Valid RIR databaseAPNIC 635 100% 67
2407:2a00:2::/48 Valid RIR databaseAPNIC 635 100% 67
2407:2a00:3::/48 Valid RIR databaseAPNIC 635 100% 67
2407:2a00:10::/44 Valid RIR databaseAPNIC 635 100% 67
103.14.183.0/24 Valid RIR databaseAPNIC, RADB 4 1%low visibility 3
103.14.181.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2
103.14.182.0/24 Valid RIR databaseAPNIC, RADB 2 0%low visibility 2

AS-SET

AS55832's PeeringDB record names no AS-SET.

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

  • ROA: origin8
  • ROA: none8
  • Route object: none16
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: origin45.64.208.0/24ROAs covering it name AS133661, not AS55832. If AS55832 should announce it, add a ROA for AS55832.4 of 673
Route object: none45.64.208.0/24Route objects for it name AS133661. Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: origin45.64.209.0/24ROAs covering it name AS133661, not AS55832. If AS55832 should announce it, add a ROA for AS55832.4 of 673
Route object: none45.64.209.0/24Route objects for it name AS133661. Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: origin45.64.210.0/24ROAs covering it name AS133661, not AS55832. If AS55832 should announce it, add a ROA for AS55832.4 of 673
Route object: none45.64.210.0/24Route objects for it name AS133661. Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: origin45.64.211.0/24ROAs covering it name AS133661, not AS55832. If AS55832 should announce it, add a ROA for AS55832.4 of 673
Route object: none45.64.211.0/24Route objects for it name AS133661. Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: origin103.245.104.0/24ROAs covering it name AS133661, not AS55832. If AS55832 should announce it, add a ROA for AS55832.4 of 673
Route object: none103.245.104.0/24Route objects for it name AS133661. Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: origin103.245.105.0/24ROAs covering it name AS133661, not AS55832. If AS55832 should announce it, add a ROA for AS55832.4 of 673
Route object: none103.245.105.0/24Route objects for it name AS133661. Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: origin103.245.106.0/24ROAs covering it name AS133661, not AS55832. If AS55832 should announce it, add a ROA for AS55832.4 of 673
Route object: none103.245.106.0/24Route objects for it name AS133661. Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: origin103.245.107.0/24ROAs covering it name AS133661, not AS55832. If AS55832 should announce it, add a ROA for AS55832.4 of 673
Route object: none103.245.107.0/24Route objects for it name AS133661. Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: none120.88.180.0/24No ROA covers it. Add a ROA for AS55832, maxLength 24.4 of 673
Route object: none120.88.180.0/24No route object for it. A route object for 120.88.176.0/20 with origin AS55832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: none120.88.181.0/24No ROA covers it. Add a ROA for AS55832, maxLength 24.4 of 673
Route object: none120.88.181.0/24No route object for it. A route object for 120.88.176.0/20 with origin AS55832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: none120.88.182.0/24No ROA covers it. Add a ROA for AS55832, maxLength 24.4 of 673
Route object: none120.88.182.0/24No route object for it. A route object for 120.88.176.0/20 with origin AS55832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: none120.88.183.0/24No ROA covers it. Add a ROA for AS55832, maxLength 24.4 of 673
Route object: none120.88.183.0/24No route object for it. A route object for 120.88.176.0/20 with origin AS55832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: none120.88.184.0/24No ROA covers it. Add a ROA for AS55832, maxLength 24.4 of 673
Route object: none120.88.184.0/24No route object for it. A route object for 120.88.176.0/20 with origin AS55832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: none120.88.185.0/24No ROA covers it. Add a ROA for AS55832, maxLength 24.4 of 673
Route object: none120.88.185.0/24No route object for it. A route object for 120.88.176.0/20 with origin AS55832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: none120.88.186.0/24No ROA covers it. Add a ROA for AS55832, maxLength 24.4 of 673
Route object: none120.88.186.0/24No route object for it. A route object for 120.88.176.0/20 with origin AS55832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55832 in the RIR database for the space.4 of 673
ROA: none120.88.187.0/24No ROA covers it. Add a ROA for AS55832, maxLength 24.4 of 673
Route object: none120.88.187.0/24No route object for it. A route object for 120.88.176.0/20 with origin AS55832 covers it (filters allowing more-specifics accept it). Add a route object with origin AS55832 in the RIR database for the space.4 of 673

Route objects not announced

Route objects with origin AS55832 whose prefix no peer sees AS55832 announce. Many are kept on purpose (backup routes, space announced only in some places).

27.123.216.0/22APNIC, RADBValid
45.64.12.0/22RADBNo ROA
103.19.136.0/23APNICValid
103.19.136.0/24APNICValid
103.19.137.0/24APNICValid
103.19.138.0/23APNICValid
103.19.138.0/24APNICValid
103.19.139.0/24APNICValid
103.24.36.0/24APNICInvalid: origin
103.24.37.0/24APNICInvalid: origin
103.24.38.0/24APNICInvalid: origin
103.24.39.0/24APNICInvalid: origin
103.250.112.0/22RADBNo ROA
120.88.176.0/20RADBNo ROA
150.107.89.0/24APNICInvalid: origin
150.107.90.0/24APNICInvalid: origin
150.107.91.0/24APNICInvalid: origin
2407:2a00::/48APNICValid
2407:2a00:1::/48APNICValid
2407:2a00:4::/48APNICValid
2407:2a00:5::/48APNICValid
2407:2a00:6::/48APNICValid
2407:2a00:7::/48APNICValid
2407:2a00:8::/48APNICValid
2407:2a00:20::/44APNICValid
2407:2a00:30::/44APNICValid
2407:2a00:40::/44APNICValid

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.