AwanCerahBGP
Home/India/AS24554
Autonomous System

Microscan Internet Limited

AS24554IndiaAPNIC · since 2006Cable/DSL/ISPPeering: Open

AS-FIVE-NET-IN

microscaninternet.com
Microscan Internet Limited website
B81/100Good

BGP report

Ranked 1,024 of 3,000 networks in India. World rank 23,992.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy7/15
  • Global visibility4/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation0/5

Computed from the route collector snapshot, IRR, RPKI and PeeringDB. How it is scored

Score history

RPKI ROA

Good
30/30

75 of 75 prefixes have a matching ROA (valid). 0 without a ROA.

Many large networks drop RPKI-invalid routes, and prefixes without a ROA are easier to hijack.

IRR route objects

Needs work
20/20

74 prefixes have an exact route object, 0 are covered by a larger one, 1 only have objects with another origin, 0 have none.

Upstreams and IXPs build prefix filters from the IRR. Prefixes without a route object can be dropped silently.

How to fix
  1. Create route (IPv4) and route6 (IPv6) objects with your AS as origin in your RIR's IRR (for example APNIC via MyAPNIC, or IDNIC), or in RADB.
  2. Group your customers in one as-set and list it in PeeringDB so upstreams can build filters automatically.
Route object with another origin (1)

Upstream redundancy

Problem
7/15

1 upstream, 0 peer, 0 downstream.

With a single upstream, any outage there cuts your whole network off the internet.

How to fix
  1. Add a second upstream from a different provider, and join an IXP to peer directly with other networks.
Upstream (1)

IPv6

Good
10/10

11 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 1 IX.

Prospective peers and upstreams look up your contacts, policy and as-set in PeeringDB.

Prefix aggregation

Problem
0/5

64 IPv4 prefixes could be summarized into 10.

Deaggregation grows the global routing table. Splitting for traffic engineering is still reasonable.

How to fix
  1. Announce the aggregate when the split is not needed. If it is intended, give every piece its own ROA and route object.

Put the badge on your website

BGP report AS24554The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS24554/rapor"><img src="https://bgp.awancerah.cloud/en/AS24554/rapor.svg" alt="BGP report AS24554"></a>
Markdown
[![BGP report AS24554](https://bgp.awancerah.cloud/en/AS24554/rapor.svg)](https://bgp.awancerah.cloud/en/AS24554/rapor)