bgpreport

Network · data from 2026-11-12

AS141778 Dream Internet Services

Registry name: DISPL-AS-AP - Dream Internet Services Pvt Ltd, PK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141778, 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.121.178.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.189.232.0/24 Invalid: origin Other origin only 2 0%low visibility 2
103.87.194.0/24 Valid RIR databaseAPNIC 673 100% 67
103.121.179.0/24 Valid RIR databaseAPNIC 673 100% 67
103.163.238.0/24 Valid RIR databaseAPNIC 673 100% 67
103.163.239.0/24 Valid RIR databaseAPNIC 673 100% 67
103.229.190.0/24 Valid RIR databaseAPNIC 673 100% 67
119.73.63.0/24 Valid RIR databaseAPNIC 673 100% 67
119.73.64.0/24 Valid RIR databaseAPNIC 673 100% 67
144.79.234.0/24 Valid RIR databaseAPNIC 673 100% 67
144.79.235.0/24 Valid RIR databaseAPNIC 673 100% 67
2001:df2:2ec0::/48 Valid RIR databaseAPNIC 635 100% 67
2001:df6:2d80::/48 Valid RIR databaseAPNIC 635 100% 67
2001:df6:85c0::/48 Valid RIR databaseAPNIC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS141778: AS141778:AS-DREAMNET. 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 (AS141778 isn't in the set, or no route object for AS141778 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 objectsAS141778 in itNot covered
AS141778:AS-DREAMNET APNIC 1124 No 14

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

  • ROA: origin2
  • Route object: none2
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: origin103.121.178.0/24ROAs covering it name AS151051, not AS141778. If AS141778 should announce it, add a ROA for AS141778.2 of 673
Route object: none103.121.178.0/24Route objects for it name AS151051. Add a route object with origin AS141778 in the RIR database for the space.2 of 673
ROA: origin103.189.232.0/24ROAs covering it name AS149870, not AS141778. If AS141778 should announce it, add a ROA for AS141778.2 of 673
Route object: none103.189.232.0/24Route objects for it name AS149870. Add a route object with origin AS141778 in the RIR database for the space.2 of 673
AS-SET: own ASNAS141778:AS-DREAMNETAS141778 isn't in AS141778:AS-DREAMNET (APNIC) once expanded. Add AS141778 to it.

Route objects not announced

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