AwanCerahBGP
Autonomous System

WoodyNet, Inc.

AS42United StatesARIN · since 2001Educational/ResearchPeering: Open

WOODYNET-1

pch.net
WoodyNet, Inc. website
A96/100Excellent

BGP report

Ranked 520 of 19,169 networks in United States, 213 of 2,087 ISPs and transit networks. World rank 4,425.

  • RPKI ROA30/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility8/10
  • IPv610/10
  • PeeringDB10/10
  • Prefix aggregation3/5

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

Score history

RPKI ROA

Needs work
30/30

416 of 419 prefixes have a matching ROA (valid). 3 without a ROA.

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

How to fix
  1. Create a ROA for every prefix in the portal of the RIR or NIR that holds it: MyAPNIC, the IDNIC member portal, the RIPE NCC LIR Portal, ARIN Online, MyAFRINIC or MiLACNIC.
  2. The ROA origin must be the AS that actually announces the prefix. Set maxLength to the announced length; a loose maxLength leaves room for sub-prefix hijacks.
Prefixes without a ROA (3)

IRR route objects

Needs work
20/20

397 prefixes have an exact route object, 16 are covered by a larger one, 6 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 (6)
Covered by a larger object (16)

Upstream redundancy

Good
15/15

101 upstream, 414 peer, 9 downstream.

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

Upstream (101)
AS2914NTT-DATA-2914AS3356LEVEL3AS1299TWELVE99AS6762SEABONE-NETAS55818MCIX-AS-APAS9002RETN-ASAS3491PCCWG-APAC-HKAS6461ZAYO-6461AS37468Angola CablesAS13030INIT7AS37271Workonline Communications(Pty) LtdAS3257GTT-BACKBONEAS3320DTAGAS3303SWISSCOMAS30844LIQUID-ASAS52320AS52320AS37474ISPA SAAS8529OMANTEL-ASAS137409GSLNETWORKS-AS-APAS4637ASN-TELSTRA-GLOBALAS37100SEACOM LimitedAS5405INTERDOTLINKAS58115SWISSIX-OUTREACHAS9957KINX-AS-KRAS39801FRANCE-IX-L3PAS7195AS7195AS4230AS4230AS4826VOCUS-BACKBONE-ASAS33891CORE-BACKBONEAS13004SOXAS50629LWLCOMAS13786SEABORNAS7922COMCAST-7922AS1257SWIPNETAS3741Dimension DataAS2518BIGLOBEAS15412FLAG-ASAS9498BBIL-APAS15802DU-AS1AS22356AS22356AS61049EXASCALEAS41095IPTPAS35625EUROFIBER-FRANCEAS23764CTGNetAS48237MOBILY-ASAS15943WTNET-ASAS1764NEXTLAYER-ASAS6910DIGI-BORDERAS23106AS23106AS60068CDN77AS1836GREENAS7713telkomnet-as-apAS7717OPENIXP-AS-ID-APAS8966Etisalat-ASAS213973BCIX-OUTREACHAS58453CMI-INT-HKAS5585IIX-ASNAS6696VERIXIAS16735AS16735AS262589AS262589AS4229ZEN-NETAS51095E1-EMEAAS24115ASN-EQIX-MLPEAS24748THINX_PolandAS263444AS263444AS20562OPEN-PEERING-ASAS15576NTSAS47498FogIXPAS9304HUTCHISON-AS-APAS39686AS-EUROFIBERAS262355AS262355AS24889MONZOON-ASAS21215UGNIAS8359MTSAS201054EPIX-PolMixAS50869FREEIX-REMOTEAS4657STARHUB-INTERNETAS12713OTEGlobeAS10099UNICOM-GlobalAS48200OPTEAMAX-ASAS55900GLBB-JPAS196959Namex-Rome-RSAS59360BBIXHK-HKAS9560APE-NZAS42689GlideAS52005NETNOD-ROUTE-SERVER-1AS10133TPIX-AS-TWAS56655GIGAHOSTAS64289MACARNEAS9371SAKURA-CAS5400BTAS20115CHARTER-20115AS56911ASN-WARIANAS32097WIIAS132213CNE-AS-APAS153759IRINN-INTERWIRE-AS-INAS44306OmoniaAS6079RCN-ASAS21859ZEN-ECNAS35168TNS-Plus-CoreAS17557PKTELECOM-AS-PK

Global visibility

Needs work
8/10

334 of 419 prefixes are seen by at least half of the full-table feeds worldwide.

Prefixes seen only partly are usually caught by filters (no ROA or route object), too specific, or announced to domestic IXPs only.

How to fix
  1. Check the ROA and route object of those prefixes, and keep them no longer than /24 for IPv4 or /48 for IPv6.
Prefixes with low visibility (85)
45.112.180.0/247.6%45.112.182.0/246.2%45.112.183.0/240.9%63.246.32.0/2413.2%63.246.33.0/240.7%63.246.34.0/2416.5%63.246.35.0/2434.4%63.246.36.0/2433.8%63.246.37.0/244.4%63.246.39.0/2429.9%63.246.40.0/2421.9%63.246.41.0/2417.6%63.246.42.0/2419.5%63.246.43.0/2414.6%63.246.44.0/2417.8%63.246.46.0/242.9%63.246.47.0/2416.4%66.96.112.0/2433.1%66.96.113.0/2421.8%66.96.114.0/2417.4%66.96.117.0/2422.6%66.96.118.0/2412.9%66.96.119.0/2440.7%66.96.120.0/2422.2%66.96.121.0/2413.2%66.96.123.0/246.2%66.96.125.0/2413.2%66.96.126.0/2426.6%66.96.127.0/240.9%66.102.32.0/2415%66.102.33.0/2413.3%66.102.34.0/2414.2%66.102.35.0/240.1%66.102.38.0/2414%66.102.39.0/2413.3%66.102.40.0/2414.8%66.102.41.0/2413.2%66.102.42.0/240.3%66.102.43.0/2419.5%66.102.44.0/2430.1%66.102.45.0/2414%66.102.46.0/240.3%66.102.47.0/241.2%66.185.118.0/2422.3%74.63.19.0/2414.4%74.63.27.0/2425%74.80.70.0/245.5%74.80.72.0/240.5%74.80.74.0/2413.2%74.80.75.0/2420.5%74.80.78.0/2418.1%74.80.79.0/2415%74.80.82.0/2439.5%74.80.83.0/2418.6%74.80.84.0/2419.3%74.80.85.0/2421.9%74.80.87.0/241.9%74.80.89.0/2433.9%74.80.94.0/2419.4%74.80.95.0/2422.1%74.80.103.0/2416.2%74.80.108.0/2417.8%74.80.115.0/2425%74.80.117.0/2413.3%74.80.125.0/2413.6%103.52.24.0/2414%103.52.25.0/2414.2%103.52.26.0/2428.6%103.52.27.0/2434.7%160.0.66.0/2413.2%160.0.68.0/2421.1%160.0.70.0/2422.2%160.0.71.0/2415.4%160.0.72.0/2415.7%160.0.73.0/2421.7%2620:171:6b::/480.3%2620:171:8b::/4849.4%2620:171:9f::/4849.4%2620:171:a7::/481.1%2620:171:b5::/4849.2%2620:171:ba::/4848.8%2620:171:bd::/480.7%2620:171:bf::/487.5%2620:171:c8::/4849.8%2620:171:cb::/4849.4%

IPv6

Good
10/10

209 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 325 IX.

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

Prefix aggregation

Needs work
3/5

210 IPv4 prefixes could be summarized into 88.

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.

Dropping invalid routes (ROV)

Good

Not seen passing on RPKI-invalid routes of other networks in sampled paths.

Not part of the score. It is inferred from sample AS paths, so the routes may come from exempted customers.

Put the badge on your website

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