AwanCerahBGP
Autonomous System

Facebook, Inc.

AS63293United StatesARIN · since 2014ContentPeering: Selective

FACEBOOK-OFFNET

A94/100Excellent

BGP report

Ranked 805 of 19,165 networks in United States. World rank 6,836.

  • RPKI ROA26/30
  • IRR route objects20/20
  • Upstream redundancy15/15
  • Global visibility10/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
26/30

155 of 179 prefixes have a matching ROA (valid). 24 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 (24)

IRR route objects

Good
20/20

179 prefixes have an exact route object, 0 are covered by a larger one, 0 have none.

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

Upstream redundancy

Good
15/15

90 upstream, 49 peer, 0 downstream.

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

Upstream (90)
AS174COGENT-174AS61580AS61580AS10084WAIA-TRANSIT-APAS37271Workonline Communications(Pty) LtdAS206186EPIX-KTW-LocalAS23951CITRA-AS-IDAS37100SEACOM LimitedAS64116AS64116AS1299TWELVE99AS58460DIGICELPNG-AS-APAS51346TOJIKTELECOM-ASAS52389AS52389AS13004SOXAS395502JCOLOAS397326SFN-ASNAS141013RISE-AS-APAS63927RISE-HKAS135814EXTREME-IX-ASAS31638ASN-LEPIDAAS51225ARMIXAS15440BaltnetaAS48326datanetworksAS52500AS52500AS52294AS52294AS52375AS52375AS52360AS52360AS37468Angola CablesAS52324AS52324AS61553AS61553AS24257JPIX-64ESAS52404AS52404AS58396DETELNETWORKS-IDAS30844LIQUID-ASAS64104AS64104AS52374AS52374AS212522SIX-ASAS37133Airtel TanzaniaAS19523BH-TELECOM-CORPAS212330IRAQIXPAS265622AS265622AS273165AS273165AS64150AS64150AS146984JPNAP-EASTAS272037AS272037AS24305EDGEIXPTYLTD-AS-APAS131976JPNAP-WESTAS263779AS263779AS265695AS265695AS32425SKB3-ARIN-BGPAS270173AS270173AS52509AS52509AS147168NTTINDONESIA-AS-IDAS61521AS61521AS52439AS52439AS32934FACEBOOKAS272806AS272806AS205140ANIX RASHAS150125MIE-AS-APAS210834LU-CIX-ITAS37545Burundi Backbone System SMAS328796Internet service provider associationAS43268SNS-ASAS328010Burkina Faso Internet EXchange Point ( BFIX)AS327875Internet service provider associationAS328452Internet service provider associationAS17828PNGDATACOLIMITED-AS-PGAS33763Paratus Telecommunications LimitedAS40300DRF-IXNET-HIAS141864MYGURUON-ASAS18155BISPIET-AS-APAS24198DATAKOMNAP-AS-IDAS395627CITY-OF-MONTGOMERY-ALAS10094UNN-BNAS6939HURRICANEAS24796NAMEX-IXPAS54980RBCOMM-1AS24482SGGS-AS-APAS49544i3DnetAS1239COGENT-1239AS37063Roke Investments International LtdAS6696VERIXIAS1257SWIPNETAS2607SANETAS58469MOCI-AS-APAS58453CMI-INT-HKAS9297COLOCITY-AS-APAS327782Metro Fibre Networx (Pty) LtdAS52025PARADOXNETWORKS-LIMITEDAS39249KICUA-ASAS22355Frogfoot Networks

Global visibility

Needs work
10/10

175 of 179 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 (4)

IPv6

Good
10/10

81 IPv6 prefixes announced.

Most mobile users and large services already run on IPv6.

PeeringDB

Good
10/10

Profile exists, listed at 80 IX.

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

Prefix aggregation

Needs work
3/5

98 IPv4 prefixes could be summarized into 44.

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 AS63293The badge updates with every snapshot.
HTML
<a href="https://bgp.awancerah.cloud/en/AS63293/rapor"><img src="https://bgp.awancerah.cloud/en/AS63293/rapor.svg" alt="BGP report AS63293"></a>
Markdown
[![BGP report AS63293](https://bgp.awancerah.cloud/en/AS63293/rapor.svg)](https://bgp.awancerah.cloud/en/AS63293/rapor)