bgpreport

Network · data from 2026-11-12

AS149994 Rego Communications

Registry name: RCL-AS-AP - Rego Communications Ltd, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149994, 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.77.101.0/24 Valid RIR databaseAPNIC 673 100% 66
103.139.144.0/24 Valid RIR databaseAPNIC 673 100% 66
103.142.68.0/24 Valid RIR databaseAPNIC 673 100% 67
103.190.82.0/23 Valid RIR databaseAPNIC 673 100% 66
103.190.82.0/24 Valid RIR databaseAPNIC 673 100% 67
103.190.83.0/24 Valid RIR databaseAPNIC 673 100% 67
103.240.5.0/24 Valid RIR databaseAPNIC 673 100% 67
202.125.72.0/24 Valid RIR databaseAPNIC 673 100% 67
103.138.214.0/24 Valid RIR databaseAPNIC 672 100% 66
2001:df0:e740::/48 Valid RIR databaseAPNIC 636 100% 70

AS-SET

PeeringDB's irr_as_set for AS149994: AS149994:AS-REGO-COMMUNICATIONS-LTD. 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 (AS149994 isn't in the set, or no route object for AS149994 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 objectsAS149994 in itNot covered
AS149994:AS-REGO-COMMUNICATIONS-LTD APNIC 9712,302 No 10

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

  • AS-SET: own ASN1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
AS-SET: own ASNAS149994:AS-REGO-COMMUNICATIONS-LTDAS149994 isn't in AS149994:AS-REGO-COMMUNICATIONS-LTD (APNIC) once expanded. Add AS149994 to it.

Route objects not announced

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

2001:470:2b7::/48ARINValid

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.